System and method for routing media

ABSTRACT

The system and method for streaming media to a viewer and managing the media comprises an enhanced service routing processor (ESRP), a real time switch management system (RTSMS), a name routing processor (NRP), and a managed media switch (MMS). The RTSMS has a reservation system. The ESRP receives media from an owner, manages the media according to media rules and order rules defined by the owner, and distributes the media to one or more switches, such as the MMS, according to the media rules and the order rules. The RTSMS is configured to receive the media rules and to receive a viewer&#39;s media request via the reservation server. The reservation system of the RTSMS processes the media request according to the media rules and builds a reservation for the requested media. The RTSMS generates the reservation to the viewer and to the NRP. The NRP receives the reservation data from the viewer and from the RTSMS. The NRP processes the reservation data and locates an MMS that can stream the media to the viewer. The NRP transmits the IP address of the MMS to the viewer and transmits the reservation data to the MMS. The viewer initiates a session or connection with the MMS using the reservation number. If the reservation data from the viewer matches the reservation data from the NRP, the MMS streams the media to the viewer.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 11/680,407, filed Feb. 28, 2007, entitled System and Method forRouting Media, which is a divisional of U.S. patent application Ser. No.10/051,406, filed Jan. 18, 2002, (now U.S. Pat. No. 7,191,244, issuedMar. 13, 2007) and entitled System and Method for Routing Media, whichis a continuation-in-part of U.S. patent application Ser. No.09/838,993, filed Apr. 20, 2001, (now U.S. Pat. No. 7,054,949, issuedMay 30, 2006) and entitled System and Method for Streaming Media, whichis a continuation-in-part of U.S. patent application Ser. No.09/766,519, filed Jan. 19, 2001, entitled System and Method forStreaming Media, the entire contents of which all are incorporatedherein by reference; and U.S. patent application Ser. No. 10/051,406,filed Jan. 18, 2002, takes priority to U.S. Patent Application Ser. No.60/263,044, filed Jan. 19, 2001, entitled Media Routing Algorithm, theentire contents of which all are incorporated herein by reference.

FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable.

COMPACT DISK APPENDIX

Not Applicable.

FIELD OF INVENTION

The present invention is related to the fields of management andadministration of media streaming.

BACKGROUND OF THE INVENTION

Real time transport of audio, video, and other data commonly referred toas “media” may be manipulated and rendered using computers and/ordigital appliances, such as a set top box. A digital appliance is aproduct that uses computer based technology and/or a telecommunicationnetwork or other packet based network to access, retrieve, interactwith, report, and/or handle media or other information.

As computers and computer based appliances gain popularity, the demandfor digital media streaming services also increases. This occurs, forexample, because digital media streaming can be used to create enhancedconsumer and business services. For example, a manufacturer of arefrigerator may install a digital appliance that connects therefrigerator's digital appliance to the Internet. A consumer can use therefrigerator's digital appliance to receive digital audio/videoexplaining how to prepare a favorite recipe.

The digital appliances and other computers can use real time mediastreaming services to render media while it is streamed from the media'sserver computer. Real time media streaming often is preferred over puredownloading since media streaming permits a consumer to view videoand/or hear audio shortly after it is requested instead of waiting for adelayed download of the complete media and a subsequent playing of themedia by the digital appliance.

Real time media streaming is difficult to implement on diverse networks,such as the Internet, corporate private networks, corporate intranets,and other packet based networking solutions. This is because real-timemedia applications typically are resource intensive and lack sufficientstate control models to ensure proper quality of service.

Enhanced media streaming services generally compound the difficultiesbecause multiple digital media streams are transmitted for enhancedservices instead of a single digital media stream, such as fornon-enhanced services. In the instances of enhanced services, currenttechnologies treat each digital media stream as an individual sessionwith little or no association to the viewer. Moreover, existing digitalmedia streaming devices focus on the technical transmission and deliveryof media, and place little control over the viewer management and mediacontent management. Finally, the current streaming video networks lacksufficient notions of network-wide and multi-level resource allocationand control, trouble detection and automatic fail-over transparent tothe viewer, and sophisticated anti-spoofing, denial of serviceprevention, and unauthorized access prevention techniques.

SUMMARY OF THE INVENTION

Enhanced media streaming services generally compound the difficultiesbecause multiple digital media streams are transmitted for enhancedservices instead of a single digital media stream, such as fornon-enhanced services. In the instances of enhanced services, currenttechnologies treat each digital media stream as an individual sessionwith little or no association to the viewer. Moreover, existing digitalmedia streaming devices focus on the technical transmission and deliveryof media, and place little control over the viewer management and mediacontent management. Finally, the current streaming video networks lacksufficient notions of network-wide and multi-level resource allocationand control, trouble detection and automatic fail-over transparent tothe viewer, and sophisticated anti-spoofing, denial of serviceprevention, and unauthorized access prevention techniques.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a streaming system in accordance with anembodiment of the present invention.

FIG. 2 is a block diagram of a reservation system in accordance with anembodiment of the present invention.

FIG. 3 is a block diagram of a name routing processor in accordance withan embodiment of the present invention.

FIG. 4 is a block diagram of a control manager for a name routingprocessor in accordance with an embodiment of the present invention.

FIG. 5 is a block diagram of the name resolution system for a namerouting processor system in accordance with an embodiment of the presentinvention.

FIG. 6 is a block diagram of the routing engine for a name routingprocessor in accordance with an embodiment of the present invention.

FIG. 7 is a block diagram of the switch manager for a name routingprocessor in accordance with an embodiment of the present invention.

FIG. 8 is a block diagram of a routing data structure used in a namerouting processor in accordance with an embodiment of the presentinvention.

FIG. 9 is a block diagram of a stream control table in accordance withan embodiment of the present invention.

FIG. 10 is a block diagram of a network status table in accordance withan embodiment of the present invention.

FIG. 11 is a table diagram of treatment table access points inaccordance with an embodiment of the present invention.

FIG. 12 is a block diagram of an active reservation table in accordancewith an embodiment of the present invention.

FIG. 13 is a block diagram of a network access table in accordance withan embodiment of the present invention.

FIG. 14 is a block diagram of a signal mapping table in accordance withan embodiment of the present invention.

FIG. 15 is a block diagram of a signal access point table in accordancewith an embodiment of the present invention.

FIG. 16 is a block diagram of a stream percent skipped table inaccordance with an embodiment of the present invention.

FIG. 17 is a block diagram of a stream rate table in accordance with anembodiment of the present invention.

FIG. 18 is a block diagram of a treatment table in accordance with anembodiment of the present invention.

FIG. 19 is a block diagram of a referring host table in accordance withan embodiment of the present invention.

FIG. 20 is a block diagram of an exception table in accordance with anembodiment of the present invention.

FIG. 21 is a block diagram of a personal identification number table inaccordance with an embodiment of the present invention.

FIG. 22 is a block diagram of a content screening table in accordancewith an embodiment of the present invention.

FIG. 23 is a block diagram of a content location table in accordancewith an embodiment of the present invention.

FIG. 24 is a block diagram of a network status table in accordance withan embodiment of the present invention.

FIG. 25 is a block diagram of a day of year table in accordance with anembodiment of the present invention.

FIG. 26 is a block diagram of a day of week table in accordance with anembodiment of the present invention.

FIG. 27 is a block diagram of a time of day table in accordance with anembodiment of the present invention.

FIG. 28 is a block diagram of a signal route choice table in accordancewith an embodiment of the present invention.

FIG. 29 is a block diagram of a class of service table in accordancewith an embodiment of the present invention.

DETAILED DESCRIPTION

Media streaming, both live and on-demand, also provides an environmentfor viewers to experience multimedia by establishing a logical,one-to-one connection between the media and the audience (a “session”).Sessions enable a rich media, interactive experience and provide afoundation for a reliable streaming service platform. Media may includeaudio, video, images, moving text messages such as stock ticker tapes,and other data. Media may include one or more media clips or a part of amedia clip. A session may include an internet protocol session, abroadband connection, or other session parameters. For simplicity,“session” may be used in some instances to mean only an internetprotocol (IP) session, only a broadband connection, or both, dependingon verbiage. In a different embodiment, more than one session can existto a given audience member simultaneously. However, improved systems andmethods are needed for implementing control features, such as real timerouting of requests for media service, dynamic matching of content tothe viewer, and enforcement of media content owners' rights anddistribution criteria.

In one embodiment, the present invention is directed to an overallintegrated and distributed media routing algorithm (MRA) that correlatesthe diverse needs of a media content owner and/or an agent (“contentowner” or “media owner”), a packet distribution network owner, one ormore viewers, and the health of a network traversed in the mediadelivery process. The MRA enables the content owner to control who viewsits content and what content is actually streamed for viewing. Inanother embodiment, the MRA enables a network owner to efficientlycontrol the network and its devices to maximize quality of service whileenabling the devices to respond automatically and transparently toviewer problems.

In another embodiment, the present invention enables content owners tocreate viewing programs that can be targeted at viewers based on theamount of information known about an individual viewer. The contentowner may create a program having one or more media items. A viewer maydesire to receive one or more of the media identified in the program.The viewing programs and viewer information may be used to dynamicallycreate a presentation tailored for that viewer. For example, thepresentation may contain a list of media from the program, possibly withor without one or more other media items, that is to be streamed to theviewer and that is combined to make a single viewing experience. Inanother example, a movie trailer followed by a full-length movie maycombine two different media to make a simple program.

A program, however, can contain media selectors that identify a set ofmedia. A media selector is used in the presentation creation processwhen the content owner desires to target different media at an audience,based on audience characteristics, and to create different presentationsfor different groups of audiences. Examples of audience characteristicsmay include the individual's sex, age, hobbies, historical viewinghabits, or other data the viewer would provide.

In another embodiment, systems and methods of the present inventioncontrol a state model, such as a basic streaming state model (BSSM), forstreaming media through enhanced communications between communicationdevices coupled over disparate packet networks, such as the Internet,intranets, virtual private networks, cable systems, frame relaynetworks, asynchronous transfer mode (ATM) networks, satellite networks,and/or any combination of interconnected, data communication networks.

The state model data identifies a viewer using a reservation, identifiesthe switch or switches from which media is streamed, the media that isstreamed, the duration the media is streamed, and other state changes inthe streaming, such as whether a stream is paused, canceled, forwarded,or reversed. If a presentation is streamed, the state model dataidentifies the presentation and the media in the presentation. The statemodel data includes stream state changes, viewing session state changes,device mode changes from a switch or signaling routing processor anderror and alarm conditions for any switch, signaling routing processor,management system, service routing processor, or other communicationdevice in the streaming system. A state model is kept for each NRP andeach MMS as described more fully below. Multiple levels of the BSSMenable event generation, tracking information, and storing informationfor transitions within a presentation from its initial generation to itscompletion or termination.

FIG. 1 depicts an exemplary embodiment of a streaming system of thepresent invention. The streaming system 102 of FIG. 1 comprises aservice processor, a management system, a reservation system, a routingprocessor, and a media switch, such as an enhanced service routingprocessor (ESRP) 104, a real time switch management system (RTSMS) 106,a reservation system 108, a name routing processor (NRP) 110, and amanaged media switch (MMS) 112, respectively, each communicating througha packet network 114. A portal 116 may communicate with the reservationsystem 108 of the RTSMS 106 via the packet network 114, and one or moreviewers 118 and 120 may communicate with the NRP 110, the MMS 112,and/or the portal 116 via a packet network 122.

The streaming system 102 has a network owner that controls the streamingsystem and controls what entities use network operators to perform workon the streaming system. For example, a network provider may build astreaming system and sell streaming services to a publishing customer.The network provider is the network owner. The network owner and thepublishing customer sell a product, i.e. media, to customers via awebsite or a contract with a web portal using the streaming system.

In some instances, the publishing customer also may be the networkprovider. This may occur, for example, where a corporate enterprise isstreaming media to its employees or customers directly. Other examplesexist.

Identifying the network owner of the streaming system 102 or anothernetwork enables the streaming system to track legal, financial,contractual, and service auditing issues associated with crossingsignaling and/or other communications, such as media, from one networkto another. For example, a first streaming network and a secondstreaming network may agree to inter-connect their networks to build alarge viewing audience. This may occur, for example, if a media ownerdesires as many viewers as possible to see its media, and the mediaowner is less concerned with what network owner the viewer uses toreceive the media.

In this example, the first network owner and the second network ownermay agree on a revenue sharing, based on what the viewer receives, andthe revenue generated from that viewer receiving the media may be splitaccording to the revenue sharing agreement. In this example, the firstnetwork owner and the second network owner cannot control each other'sservice, network distribution rules, and/or other routing or operationalprocesses. Thus, the first network owner and the second network ownerare required to agree on the revenue sharing and how their networks willinterconnect in order to provide distribution of media and receiverevenue based on that distribution.

The streaming system 102 also enables a media owner to identify aprogram or a portion of a program that is made available for streaming.The program typically identifies the sequencing, whether sequential,parallel, timing, or other, in which media clips are to be streamed,where the media clips are to be placed, and, in some instance, to whomthe media clips can be transmitted.

A program may have a list of media, an order, and/or other media rules.The program may also have program creation rules and/or program routingrules. Network distribution rules generated by the owner and/or operatorof the streaming system 102 (hereafter, “network owner”) or one or moreother packet network suppliers also may be associated with the program.The network distribution rules, the media list, the order, and any otherspecial media rules, such as program creation rules and/or programrouting rules, govern the transmission of the media for a program.

Program creation rules are defined by a media owner. Program creationrules may identify if a program can be created from one or more otherprograms and how the one or more other programs may be combined. Forexample, a program may have program creation rules identifying whichindividuals are allowed to alter the program rules, listings ofidentifications of other media owners that have agreed to share media,and other administrative data.

Program routing rules are defined by the media owner. Program routingrules define where and/or how media may be routed. Program routing rulesmay be superceded by network distribution rules.

Network distribution rules are defined by the network owner and/or oneor more other packet network suppliers. Network distribution rules areused to manage capacity, load, bandwidth, switch resources, and/or otherevents and/or resources, including resources for sessions andconnections. For example, a program can be configured to stream tenminutes of a sitcom based media, insert an advertisement, and thenreturn to the sitcom based media. The publisher may define the programrules to transmit greater than 30 frames per second, but the networkdistribution rules may be restricted to 30 viewing frames per second bythe network supplier. The program would not be streamed since itviolated the network distribution rules. The network distribution rulesmay manage and/or identify resources needed to transfer media betweenthe streaming system 102 and one or more other packet networks.

The media list may include one or more different media referencesidentifying one or more media clips and one or more different types ofmedia. For example, the media list may contain media names or othermedia references. The media list may include references to one or moreof recorded media, live media, a media alias, a media selector includingan advertising selector, and/or other media.

Recorded media typically directly references a media file name. Livemedia typically has connection instructions to a live ingress switch. Amedia alias typically references one or more other media clips. A mediaselector typically contains rules identifying how to select one or moreof several possible media clips. An advertising selector is a type ofmedia selector used to select an advertising media clip.

Each type of media may contain one or more of the above-statedidentifiers or other identifiers. Additionally, each media clip may havea title assigned to it by the media owner.

An order is a request by a paying or collecting entity for the networkowner to provide some sort of streaming or related service, such asstorage. Typically, the order is made by a paying or collecting entity,such as a publisher, another streaming network service provider, aviewer, a private company, an advertising service, or another entitythat desires to enter into a contract with the network owner forstreaming service or related services, such as real time usagereporting.

An order may be associated between multiple entities. For example, apublisher may be primarily responsible for payment to the network ownerfor streaming services, but an advertiser has agreed to pay the networkowner based upon the number of people viewing their ads. Thus, twopaying entities and one collecting entity are associated with the order.In this example, an entity can be both a paying entity and a collectingentity. For example, a publisher can pay for streaming services and alsocollect a portion of the fee generated by streaming media.

An order can contain several order components, such as service billingrules, storage billing rules, collection rules, viewing rules,settlement rules, and other fiscally important information. This fiscalinformation allows a network owner to generate an invoice for streamingservices rendered. The associated invoiced revenue may be collectedbased on the fiscal information, and other collection entities, such aspublishers and other networks, may be paid based on that fiscalinformation.

Service billing rules normally are related to making the media availablefor viewing. Multiple media items can be associated to a single servicerule. Service rules allow the publisher to describe to the network ownerhow the media viewing will be paid. For example, pay-per view media mayrequire the viewer to pay for the service. A fee for service may requirethe publisher to pay a fee based on the number of data bytes transmittedto all viewers for a defined period of time. An advertising revenueshare may require the network owner to collect a percentage of theadvertising revenue generated by the program being viewed. Other paymentmethods and combination of payments may be used.

An order also can contain storage rules for determining where the mediaor program will be located and the costs associated with the physicalstorage of the media. Storage rules allow the publisher to target mediato MMS locations that they believe will provide the most streamingservice. For example, advertising media that is localized to themid-west of the United States of America could be located on only MMSswithin that region. Storage rules can specify a single MMS device, anoffline storage location that is not attached to any MMS, multiple MMSdevices, all MMS devices, and other networks that can provide the samemedia, if needed. Storage rules also allow the network owner to bill forthe amount of storage a publisher uses on a periodic basis, such as anaverage daily storage use. A storage order can have multiple media andprograms attached to it.

An order may contain collection rules identifying which entity orentities are collecting a payment for services rendered. For example, aservice rule that designates pay-per-view might require an immediatecredit card payment by the viewer. The collection rule may identify thecredit card collection agency, collection account, and other vitalsettlement data for the processing of the viewer's credit card. Inanother example, the viewer may select pay-per-view and simply be billedthe amount on their monthly cable bill. Collection rules also apply tothe invoicing of charges to corporate type accounts, such as how soonpayment is due after the invoice is printed. Collection rules focus onreceiving the payment portion of the transaction. Multiple collectionrules may be applied to a single order.

An order may contain viewing rules for the media and/or programs thatare attached to it. Viewing rules associated with an order allow thepublisher to determine who sees the media or program based on theviewer's account status. For example, a viewing rule for a subscriptionbased service in which a viewer is 90 days or more behind in paymentsmight block the service.

In another example, if a viewer selects a pay-per-view media item thatrequires a credit card payment, and the credit card collection agencyreturns a code declaring the card is over its limit, the viewing rulemight block the service. Order viewing rules typically are associated toa credit rating or current collection status of an account for theperson requesting to view the media or the publisher wishing to make themedia available for distribution.

An order can contain settlement rules for determining how collectionsare divided and which entities participate in the settlement. Forexample, a program may be created by a publisher in which advertisersagree to pay the publisher and the network owner for targeting theiradvertising to a specific set of viewers. The viewer is allowed to viewthe program free of charge, except the viewer will receiveadvertisements. The settlement rules would describe the agreed uponadvertising rates that will be applied on a per viewer basis, thepercentage or fixed fee being supplied to the network owner for eachviewer, and other settlement data.

There may be a many-to-many relationship between an order and a program.That is, one program or multiple programs may appear in a single serviceorder, and a single program may appear in a one order or multipleorders. For example, in the former instance, an order may associatemultiple programs that are the publisher's $4.99 pay-per-view programsfor distribution in the United States. Whereas, in the latter instancefor example, a single program may be associated with one order forpay-per-view customers and another order for subscribers.

In some embodiments, the program has a program identification. Theprogram identification may be used to track use of the program, such ashow many times the media for a program is streamed and the number ofusers receiving that program. Additionally, the program identificationmay be used to track other attributes associated with the program, suchas viewer attributes associated with the viewer receiving the media,streaming times, other media or programs streamed with a particularprogram, and/or other tracking purposes.

When a program and its order are complete, it may be published.Publishing is the act of making a program available on the streamingnetwork 102 for distribution to one or more viewers via a switch, suchas the MMS 110.

After a program is published, a presentation may be generated based onthe program. A presentation results from applying a viewer profile to aprogram, including the program's order and any other media rules, at thetime a reservation is made for the program by the viewer. A viewerprofile may be any set of attributes of interest for a viewer and theirvalues. Thus, the presentation typically is customized for an individualviewing session, and the program and the viewer profile are what areused to generate the presentation.

The presentation may identify the media to be streamed to a viewer forthe requested program and the resources needed to stream the media. Thepresentation also may include special instructions, such as specialmedia sequencing instructions, late binding media instructions, and/orspecial routing instructions.

In one embodiment, the presentation contains one or more programidentifications. The program identification may be used to track one ormore programs identified for the presentation and/or other attributesfor the viewer, the resources used for the presentation or itsstreaming, reporting associated with the program or other media orprograms associated with the program, and/or other purposes. Forexample, a viewer may attempt to view multiple programs within a singlereservation. However, a media owner for one of the programs may wantreports identifying how many people received the program and thestatistics for that streaming. Therefore, the program identification isused to provide tracking and reporting on the program level, as opposedto the reservation level. The program identification enables thestreaming system 102 to track and report individual programs and theirusage.

The presentation typically is transmitted to an NRP in a reservationalong with the reservation identification. In some instances, the viewerprofile and/or a reservation window may be included in the reservation.The reservation window is the starting time and the ending time forwhich a reservation and the resources for a reservation are valid andavailable for a viewing session. Preferably, a viewing session should bestarted and completed within the reservation window. Although,enforcement may be configured as a matter of network owner policy.

At the time a reservation is made for the program by the viewer, a playscript also is created. The play script contains a list of one or moremedia references for the presentation and a reservation identification.In one embodiment, the play script contains one or more universalresource locators (URLs), and each URL identities a media clip andcontains the reservation identification.

The play script may be formatted according to the type of player theviewer is using and may contain information identifying how to contact aresource, such as the MMS 110 or a device on the MMS, to receive themedia. In some instances, such as some configurations where the vieweris a set-top box, the device streaming the media to the set-top box mayinitiate the connection to the set-top box, and information identifyinghow to connect to the resource is not needed. The play script typicallyis transmitted to a viewer.

The ESRP 104 enables media owners to place media on the ESRP fordistribution to various switches, such as to various multimedia switchesin the streaming system 102. The ESRP 104 allows each media owner tocreate a program for the media, including creating a list of media, withone or more different types of media or one or more different mediaclips and the media rules to determine the sequence in which the mediaclips are to be streamed, where the media clips are to be placed, and insome instances to whom the media clips can be transmitted.

The ESRP 104 also enables a media owner and/or a publishing agent of theowner (hereafter “media owner”) to generate the settlement rules thatdefine who will be billed or credited when media is transmitted to aviewer or another device and the terms of the bill or credit. Forexample, a media owner may have a contract with a service provider, andthe service provider will share in the revenue generated by viewersviewing the content. Alternately, the media owner may have to pay theservice provider for use of an amount of bandwidth when the media istransmitted. In addition, part of the media sent to a viewer may includeadvertisements, and the media owner can define a rule to bill theadvertising entity a dollar amount each time the media is transmitted.

The ESRP 104 also enables a media owner to create special viewing rulesand/or routing rules for the program. The viewing rules and/or routingrules may identify any restrictions or other customizations, such asgeographic or age restrictions, preferred language, or substitutions onthe streaming of the program. For example, if a football game is aprogram, the game may be blocked from a specific region when thestreaming is free, but not blocked if the game is part of a subscriptionor pay-per-view service. In this instance, the media owner may generatetwo or more different orders for the same program, and a viewer 118 or120 would be blocked or not blocked from the program depending on whichorder the viewer was attempting to use.

The ESRP 104 publishes programs when the programs and the orders for theprograms are complete. Thus, when a program and its order are complete,the ESRP 104 may transmit the media identified in the program to one ormore switches, such as the MMS 112, according to one or more media rulesso that the program is available to be streamed to a viewer. The ESRP104 also publishes the program, including a program identification, amedia list for the program, and the media rules for the program, to theRTSMS 106.

One or more ESRP devices may exist in the streaming system 102. One ESRPis depicted in FIG. 1 for clarity.

The RTSMS 106 accepts programs and their respective orders from the ESRP104 when the programs are published. The RTSMS 106 determines theswitches or other communication devices on which the programs reside.The RTSMS 106 receives the media list, the media rules, the programidentification, and any associated orders for the program from the ESRP104.

The RTSMS 106 receives signaling from a viewer 118 or 120. Thissignaling may be routed to the RTSMS 106 via a portal 116 or anothertype of communication device. The initial signaling from the viewer 118or 120 typically is a request for a program or programs. However, asimple request for an individual media or list of media may be honoredin some embodiments.

The RTSMS 106 processes the signaling to determine if the requestedprogram is available (or the media can be found in, and an appropriatematch for, a program) and if the program has restrictions applied by themedia owner and/or network operator and locates an NRP 110 within thestreaming system 102 that is capable of processing the viewer's request.The RTSMS 106 then generates a customized play script for the requestedprogram to the viewer. The play script may include the requested media,such as one or more media clips, and additional media, such as one ormore advertisements, either as media clips, banner advertisements, orother types of advertisements. The play script is formatted as theoutput of a presentation generator process and is formatted for thelanguage/format of the viewer 118 or 120. For example, a viewer 118 or120 using the Real Network's Real Player may require a synchronizedmultimedia integrated language (SMIL) file based play scripts, and theplay script would be formatted as such.

The RTSMS 106 builds a reservation for the viewer 118 or 120 for thecustomized play script and temporarily reserves the resources identifiedby the presentation generator process for use by the viewer 118 or 120.The RTSMS 106 transmits the reservation along with its presentation tothe selected NRP 110 and transmits the customized play script to theviewer 118 or 120.

The reservation uniquely identifies the viewer 118 or 120 and thecustomized play script. In one embodiment, a separate URL identifieseach name on a play script for a presentation, and the reservation has aunique reservation identification that is located in each URL. The URLsare transmitted to the viewer 118 or 120 using the play script, and theviewer can use the play script to initiate a session with a switch. Areservation is a feature that enables the streaming system 102 toreserve system resources, such as switches, processors, or media, eithernow or in the future, to ensure a quality media experience.

The reservation system 108 receives a request from the portal 116 onbehalf of the viewer 118 or 120 for viewing a media and/or presentation.The reservation system can receive additional information from the RTSMS106, such as past history of the viewer 118 or 120 or products/servicesin which the viewer has used or participated. The incoming request canbe tailored by the RTSMS 106 to append any available data it has on theviewer 118 or 120. The incoming data is processed through the programrules to generate the presentation. For example, the viewer 118 or 120may desire to view a training video for an investment. The RTSMS 106 mayappend the current financial value of the viewer 118 or 120 and use themedia selectors in the presentation's supplemental programs forinvestment vehicles that are offered.

The reservation system 108 generates the reservation and forwards it tothe NRP 110 along with log information. The reservation system 108generates and maintains the unique identifiers for every request itreceives. Requests that are not fully processed also are recorded andlogged for record keeping purposes. The reservation system 108 enablesthe network owner to establish the time period in which a reservationwill be valid for the viewer 118 or 120 to completely view the media.

The RTSMS 106 maintains historical, current, and future views ofprocessing tables that reside in all NRPs in the streaming system 102,including the NRP 110. These tables and the associated data stored bythe RTSMS 106 enable the NRPs to determine a switch or switches, such asthe MMS 112, that can provide the requested program to a viewer 118 and120.

The RTSMS 106 collects state model data, such as BSSM data, from allNRPs and switches in the streaming system 102, including the NRP 110 andthe MMS 112. The state model data identifies a viewer using areservation, identifies the switch or switches from which it isstreamed, identifies the media that is streamed, the duration the mediais streamed, and other state changes in the streaming, such as whether astream is paused, canceled, forwarded, or reversed. If a presentation isstreamed, the state model data identifies the presentation and the mediain the presentation. The state model data includes stream state changes,viewing session state changes, device mode changes from the NRP 110 andthe MMS 112, and error and alarm conditions for any MMS, NRP, RTSMS,ESRP, or other communication devices in the streaming system 102. Astate model is kept for each NRP and each MMS as described more fullybelow.

The RTSMS 106 can be configured to dynamically select advertising orother content. For example, the RTSMS 106 may be configured for use byan investment management company that manages several different fundsand has several different analysts associated with each fund. Forexample, a person using a viewer may have money in funds A and B but notC or D, and the total value of the viewer's ownership in funds A and Bis between $100,000 and $200,000. The RTSMS 106 may use the rule set inthe monthly fund program to dynamically place media clips that containthe A and B fund managers discussing recent performance, analystsdiscussing the outlook for the goals of the A and B funds, and advicecustomized for that investment level in the presentation. Whereas, ifthe person using the viewer has $50,000 in an IRA in fund C, the RTSMS106 may use the rule set in the same monthly fund program to dynamicallyplace media clips showing the C fund managers discussing recentperformance, analysts discussing the outlook for the fund's goals, and atax expert discussing the implications of IRA tax law changes thataffect IRAs at that level in the presentation.

The ability to dynamically select content can result in a different costbasis for different presentations. For example, in the above examples,expenses of three dollars may be incurred for the A and B analysts'media clips, and revenue of two dollars may be incurred for the Canalyst's media clip.

In one embodiment, the RTSMS 106 is configured to dynamically selectcontent using statistical information. The RTSMS 106 also may beconfigured to bill or credit entities according to order rules and/orthe statistical information.

Statistical identification is the determination of the value of one ormore different possible attributes of a viewer. For example, statisticalidentification may be used to create a viewer profile, or attributesfrom an already created viewer profile may be used for a statisticalidentification. The identification of viewer could be, for example, thatthe viewer is within a geographic area, such as a zip code or anNPA-NXX, that the viewer is within an age group, such as 18-23 years,that the viewer can watch movies of a designated media rating, such asPG, PG-13, or Y-14, that the viewer is male or female, the viewer'smarital status, what funds the viewer has invested in, what departmentsthe viewer works for, and/or other personal data relevant to thepublisher of the program.

In one embodiment, if the program requires statistical identification ofthe viewer, the RTSMS 106 may look up previously collected informationabout the viewer. If no information exists, the RTSMS 106 may instructthe portal 116 to collect the required information or supply defaults ifthe information is not required. If the viewer does not supply therequired information, the RTSMS 106 can be configured to reject theviewing request.

The RTSMS 106 provides reporting capabilities. The reports may includenear real-time reports of what media is streamed and the associatedstatistical information, including demographics, on the entire network.The RTSMS 106 may provide network management capabilities, includingoperational measurement collection, threshold alarming, and trendanalysis.

The RTSMS 106 also collects logs and billing data from the ESRP 104, theNRP 110, and the MMS 112. The billing data may include the order dataand the reservation data and may include state model data. The logs area record of the events that have occurred and are viewable andauditable. Logs are generated by many processes, such as one or moremedia servers on one or more stream casters of one or more MMSs, one ormore NRPs, one or more MMSs, one or more portals, and one or more ESRPs.

The RTSMS 106 processes the logs, the billing data, and the state modeldata and creates a message sequence detail record (MSDR). The MSDR is acollated view of log and state model data for a reservation. The RTSMS106 creates an MSDR for every reservation by obtaining information fromthe reservation order log, the MMS 112 logs, and the NRP 110. Thistypically is accomplished using the reservation identification that iscontained in every entry for log and billing data. The MSDR represents abillable event record that will be used for revenue settlement purposes.

The RTSMS 106 processes the MSDRs and creates bills in accordance withthe media rules and orders identified in the programs. Logs, state modeldata, and billing data for a single viewer 118 or 120 may come from morethan one NRP, more than one MMS, and more than one ESRP.

The RTSMS 106 collates all of this data into a single MSDR for areservation identifying the viewer 118 or 120 using the reservation dataand the state model data. By using reservation data for a viewer 118 or120 and/or a program, the streaming system 102 is able to service amedia request from more than one switch or more than one stream casteron a switch. Prior systems could not adequately use multiple switches toprovide media programs to a single viewer and clearly identify billingdata because the prior systems could not adequately track and collatebilling information from multiple switches. Prior systems typicallyservice a media request from a single media server in these instances.

The RTSMS 106 receives from the MMS 112 and any other switches streaminginformation blocks (SIBs) comprising signaling, event and billinginformation associated with each streaming session. The RTSMS 106combines the information in the SIB with fixed attributes, such as aviewer identification associated with a reservation identification, aviewer profile, a viewer location, a media category being viewed, andother data to create the MSDR. The RTSMS 106 uses the reservationidentification in the SIBs as the key to determining all SIBs for apresentation or a streaming event. The RTSMS 106 uses the reservationidentification to collate all SIBs for that presentation or streamingevent into the MSDR. The MSDR therefore represents the data used forbilling records and reports for a presentation or other streaming event.The MSDR creates an auditable event record that is used for operationalmeasurements and billing. The RTSMS 106 can use the MSDR with rulesidentified in an order to determine bills and credits to be appropriatedto various entities.

The RTSMS 106 receives from the NRP 110 and the other routing processorspertinent NRP log records comprising reservation routing requests andtheir granting, refusal, transfers, and forwarding, includingidentification of switches streaming media and the associated sessiondata. The RTSMS 106 stores the NRP log records and retrieves the NRP logrecords, such as if needed for auditing purposes.

The RTSMS 106 may be configured with a human machine interface (HMI)that enables a network operator to access the RTSMS or anothercommunication device in the streaming system 102. The network operatorcan use the HMI to load new software to, for example, the MMS 112, toupgrade configurations, or to provide other maintenance, such as toexecute functions specifying capacity to be used, to identify whenswitch components will be taken out of service for maintenance, tocreate new products or services for use by a media owner, and/or toissue test presentations to specific media servers on an MMS.

An RTSMS 106 may be a local or regional RTSMS. The RTSMS 106 of FIG. 1is depicted as a local RTSMS. One or more RTSMS devices may exist in thestreaming system 102. One RTSMS 106 is depicted in FIG. 1 for clarity.

The NRP 110 receives a request from a viewer 118 and 120 and processesthe request. The request contains the identification of the NRP to whichit is sent, and the reservation identification generated by the RTSMS106. For example, the NRP 110 reservation may be an NRP host name or anNRP IP address, and the reservation identification may be a reservationnumber. The NRP 110 also receives the reservation from the RTSMS 106.

The NRP 110 processes the request and compiles a list of switches thatmay be able to provide the requested media to the requesting viewer 118or 120. The NRP 110 identifies an ordered list of switches, and attemptsto select a switch based on network distribution rules. For example, thenetwork supplier can choose to route on the best possible quality ofservice that can be provided to the viewer 118 or 120, to route ongeographic factors, the time of day, the day of the week, the day of theyear, or the access provider, or to route on overall network conditions.

The NRP 110 communicates with the switches to determine which switch, ifany, can provide the requested media. For example, the NRP 110 may startwith the best identified switch and, if not available, communicate withthe next-best identified switch. The NRP 110 transmits to the viewer 118or 120 an address, such as an IP address, of the switch that can providethe requested media. In one embodiment, if no switch can be found in thefirst pass, then a bumping algorithm can be invoked that may bump acurrent stream from a switch. The rules for bumping can be establishedby the network operator, for example, according to service agreementswith publishers.

In one embodiment, a request is sent from the viewer 118 or 120 to theNRP 110 for each media clip on the play script. Thus, the NRP 110 mustdetermine a switch that can stream the particular media clip of the playscript to the viewer 118 or 120 separately for each media clip on theplay script. Each time the NRP 110 determines the switch that canprovide the media clip, the NRP transmits an IP address of the switch ora communication device, such as a stream caster on the switch, to theviewer 118 or 120.

For example, if a play script identifies two media clips, the viewer 118or 120 transmits a media locator request to the NRP 110 for the firstmedia clip. The NRP 110 determines a switch that can provide the firstmedia clip and transmits an IP address of that switch to the viewer 118or 120. After the viewer 118 or 120 receives the first media clip in asession with that switch, the viewer could send another media locatorrequest to the NRP 110 for the second media clip. The NRP 110 determinesa switch that can provide the second media clip and transmits an IPaddress of that switch to the viewer 118 or 120. The viewer 118 or 120then receives the second media clip in a session with that switch.

The switch that streams the first media clip may be the same as ordifferent from the switch that streams the second media clip. Also,multiple devices on one switch, such as two different stream casters ona switch, each may stream one of the media clips, or one device on theswitch may stream both media clips.

In another embodiment, the NRP 110 can be configured to determine aswitch that can provide all media clips on a play script. In thisembodiment, a single determination is completed by the NRP 110 in whichthe NRP locates a single switch that can stream all media clips on theplay script to the viewer 118 or 120.

The NRP 110 receives and processes signaling from each MMS and eachother switch before, during, and after media is streamed. If a switch orpart of a switch fails or can no longer maintain stream quality during amedia streaming, the switch may notify the NRP 110, and the NRP maydetermine a different, second switch that can provide the requestedmedia. The NRP 110 then may direct the failing switch to route thestreaming session to the second switch.

The NRP 110 initiates a state model for each viewer and each streamedmedia. The state model comprises a view of an entire media streamingevent to a viewer 118 or 120, including which switch or switchesstreamed media to the viewer, the time each media request is sent toeach switch, any alarm or error events for a switch, such as alarms orevents that may require another switch to provide the requested media,and transfers or re-connections to another switch to provide therequested media. The state model may include an identification ofdevices within the switch that provide the requested media to the viewer118 or 120, such as which stream caster or stream casters within an MMS112 stream media to the viewer.

The state model in the NRP 110 includes a switch identification and themajor states of a session or a connection, sometimes referred to aspersistent states. Major states may include the reservation acceptance,an initiation of a session or connection, a termination of a session orconnection, and other persistent states. The state changes may bereceived when setup or teardown messages are received by the MMS 112 andat other states. Each state change preferably is identified with thereservation identification.

The NRP 110 transmits an NRP log to the RTSMS 106 when the media for apresentation has been streamed to a viewer 118 or 120, if an erroroccurs during a streaming session, and periodically during a streamingsession. The period during the streaming session is configurable. In oneembodiment, the period is every five minutes. Another period or defaultmechanism may be used, such as the occurrence of an event.

The NRP 110 may use the domain name server (DNS) protocol to receive amedia locator request from the viewer 118 and 120 and to return an IPaddress of the stream caster in the MMS to which the viewer will connectfor a session. Other protocols, such as session initiation protocol(SIP) or H.323, may be used.

One or more NRP devices may exist in the streaming system 102. One NRPis depicted in FIG. 1 for clarity.

The MMS 112 streams media to a viewer 118 or 120. The MMS 112 hascommunication devices, such as one or more stream casters and one ormore media servers, that provide requested media to a viewer 118 or 120.The MMS 112 monitors the communication devices, such as one or morestream casters and one or more media servers, within the MMS so that theMMS can determine if it can provide a requested media.

The MMS 112 processes signaling from the NRP 110 and returns signalingto the NRP 110. The MMS 112 receives signaling messages inquiring if theMMS can stream media to a viewer 118 or 120. The MMS 112 processes thatinquiry, determines if it has the resources, such as a stream castertype, network bandwidth, disk space, and a media server, to stream themedia, and responds with a message to the NRP 110 accepting or denyingthe inquiry.

The MMS 112 receives reservation data from the NRP 110 for a media clipin a presentation. The MMS 112 may be configured to receive reservationdata from the NRP 110 and a reservation identification from the viewer118 or 120. In that instance, the MMS 112 may authenticate thereservation identification using the reservation data from the NRP 110to determine if the reservation identification is valid. In oneembodiment, if the MMS 112 receives the reservation identification forthe presentation from the viewer 118 or 120 within a configurable periodof time, and the reservation identification is valid when compared tothe reservation data from the NRP 110, the MMS 112 will stream the mediato the viewer. In another embodiment, if the viewer 118 or 120 does nottransmit the valid reservation identification to the MMS 112 for thatpresentation, fails authentication, or if the viewer transmits thecorrect reservation identification but not within the configurableperiod of time, the MMS will not stream the media to the viewer. In thatinstance, the MMS 112 will reject the request from the viewer 118 or120, and a session will not be initiated. The rejection is transmittedto the RTSMS 106.

The MMS 112 may have a stream routing processor (SRP) or another type ofprocessor or monitor that processes requests for media using the currentstate of the switch, such as available bandwidth, bandwidth necessary toprovide a requested media, hardware and software version compatibility,disk space capacity, the current operating mode of the MMS, and/or otherstate factors. The MMS 112 monitors the delivery of each media streamand the status of switch systems. The MMS 112 may detect an imminentfailure of one or more communication devices in the MMS if such afailure occurs, such as a failure of a stream caster's media server. TheMMS 112 can transmit this data to the NRP 110.

If a stream caster, a media server on the stream caster, or anothercommunication device in the MMS 112 fails, the MMS can transparentlytransfer all streams in-progress to another stream caster or to anothermedia server on the stream caster, if one is available. The transfer andthe continued streaming of the media are not recognizable by the viewer118 and 120.

If a communication device on the MMS 112 fails and another is notavailable on that MMS, the MMS notifies the NRP 110 and the RTSMS 106.In response, the MMS 112 will receive and process from the NRP 110 amessage instructing the MMS to route the stream to another MMS. The MMS112 then will route the stream to the identified MMS. The transfer andthe continued streaming of the media are transparent to the viewer 118and 120.

The MMS 112 has a state model in which the MMS stores information andstate changes for a viewing session of a presentation. The MMS 112stores and reports each state change at the appropriate level. Forexample, the state model stores information and state changes for theinitiation of a session, the termination of a session, and viewingevents. Viewing events are events triggered by a viewer that affect themedia streaming of the presentation. Viewing events may be, for example,a play, a pause, a stop, a forward, a cancel, a complete, or a rewind.

If the MMS 112 transfers a stream to a different stream caster or mediaserver within the MMS, that event is noted in the state model, and thestate model stores the information and state changes for the new streamcaster or media server. If the MMS 112 transfers a stream to a differentMMS, that event is noted in the state model.

The MMS 112 transmits to the RTSMS 106 stream information blocks (SIBs)for each stream session event and for each viewing session event. TheSIB comprises information associated with the streaming session from theMMS 112 to the viewer 118 or 120, including the reservationidentification, an identification of the MMS or other switch, the streamcaster and media server used, the media streamed, the presentationidentification, the packet data path for each session, the equipmentused for the streaming, and/or viewing events, such as a pause orrewind. One or more of the previous items may be used or not used in theSIB. If more than one stream caster or media server on one or morestream casters is used, that information also may be specified in anSIB.

An SIB is created when a viewing session is initiated, when a viewingsession is terminated, when new media is presented, during a streamingsession at configurable periods, and/or when other viewing events occur,such as a pause, stop, rewind, forward, or error. The SIBs aresubsequently transmitted. In one embodiment, the period is configured atfive minutes. Other periods, different periods, or defaults, such as anevent, can be used.

One or more MMS devices may exist in the streaming system 102. One MMS112 is depicted in FIG. 1 for clarity.

The packet networks 114 and 122 each are a communication network capableof transmitting data, such as signaling or media streaming, to or from acommunication device in the streaming system 102, such as to or from theESRP 104, the RTSMS 106, the NRP 110, the MMS 112, the portal 116,and/or the viewers 118 and/or 120. The packet networks 114 and 122 maybe the Internet, an intranet, a virtual private network, a cable system,a frame relay network, an ATM network, a satellite network, and/or otherpacket based networking solutions. In one embodiment, the packet network114 is a private network accessible by the ESRP 104, the RTSMS 106, theNRP 110, the MMS 112, and an authorized portal 116. In anotherembodiment, the packet network 122 is a public network.

The portal 116 is a processor, such as a server, configured tocommunicate with a viewer 118 or 120. The portal 116 managescommunications between the viewer 118 or 120 and the RTSMS 106. Forexample, the portal 116 may transmit viewer media selections to theRTSMS 106 and may transmit reservation data originating from the RTSMSto the viewer 118 or 120. The portal 116 may be a web-based processor, aset top processor, or another type of processor.

The viewer 118 or 120 may use the hypertext mark-up language (HTML) IPprotocol via IP sessions using a web browser that can be serviced by aweb-based server. The viewer 118 or 120 also may use broadband protocolsvia a broadband connection using a set top box appliance communicatingwith a set top server. A set top server can process various protocols,including session initiation protocol (SIP), which is an InternationalTelecommunications Union (ITU) H.323 series protocol. The portal 116 ofFIG. 1 is authorized to transmit messages to the RTSMS 106.

The viewers 118 and 120 are any communication device capable oftransmitting and/or receiving signaling and/or media. The viewers 118and 120 may be broadband based viewers or narrowband based viewers. Forexample, the viewers 118 and 120 may have a browser configured tocommunicate using a web based protocol such as hypertext transferprotocol (HTTP). Also, the viewers 118 and 120 may have a media playerconfigured to play media that is streamed to the viewers. In addition,the viewers 118 and 120 may have a set top box or another digitalappliance configured to play media streamed from a cable televisionprovider, a digital satellite provider, or another type of provider.

In some embodiments, the NRP 110 requests the MMS 112 to provide a mediaclip. In this embodiment, if the MMS 112 can provide the requested mediaclip, the MMS responds to the NRP 110 that it can provide the requestedmedia clip. The NRP 110 transmits a message to the viewer 118 or 120identifying the MMS 112 as providing the media clip. The viewer 118 or120 initiates a session or a connection to the MMS 112, and the MMSprovides the requested media clip.

In other embodiments, the NRP 110 requests the MMS 112 to providemultiple media clips. In this embodiment, if the MMS 112 can provide therequested media clips, the MMS responds to the NRP 110 that it canprovide the requested media clips. The NRP 110 transmits a message tothe viewer 118 or 120 identifying the MMS 112 as providing the mediaclips. The viewer 118 or 120 initiates a session or a connection to theMMS 112, and the MMS provides all of the requested media clips withoutfurther action from the NRP 110. In this embodiment, in one instance,the viewer 118 or 120 initiates a single session or connection with asingle setup message, and the MMS 112 streams all requested media clipsbefore the session or connection is terminated. In another instance, theviewer 118 or 120 transmits a separate setup message and teardownmessage for each media clip, and the MMS 112 stops streaming media afterthe last requested media clip is streamed.

In other embodiments, the NRP 110 requests the MMS 112 to providemultiple media clips. In this embodiment, if the MMS 112 can provide therequested media clips, the MMS responds to the NRP 110 that it canprovide the requested media clips. The NRP 110 transmits a message tothe viewer 118 or 120 identifying the MMS 112 as providing the mediaclips. The viewer 118 or 120 initiates a session or a connection to theMMS 112, and the MMS provides all of the requested media clips. However,after each media clip is streamed, the viewer 118 or 120 communicateswith the NRP 110 to receive authorization to initiate a session with theMMS 112. The NRP 110 communicates with the MMS 112 to confirm that theMMS 112 can provide the next media clip. The MMS 112 acknowledges to theNRP 110 that it can provide the next media clip, and the NRPacknowledges to the viewer 118 or 120 that the MMS 112 can provide thenext media clip. The viewer 118 or 120 then transmits another setupmessage to the MMS 112 to obtain the next media clip.

In some embodiments, the NRP 110 requests the MMS 112 to provide apresentation. In this embodiment, if the MMS 112 can provide therequested presentation, the MMS responds to the NRP 110 that it canprovide the requested presentation. The NRP 110 transmits a message tothe viewer 118 or 120 identifying the MMS 112 as providing thepresentation. The viewer 118 or 120 initiates a session or a connectionto the MMS 112, and the MMS provides the requested presentation.

In some instances in this embodiment, the viewer 118 or 120 transmits asetup message for each media identified in the presentation play script,receives the media, and tears down the session or connection for thatmedia. The viewer 118 or 120 then immediately transmits another setupmessage to the MMS 112 to get the next media on the play script. Theviewer 118 or 120 receives the media and tears down the session orconnection. This process continues until the viewer 118 or 120 hasreceived all media on the play script. In other instances in thisembodiment, the viewer 118 or 120 transmits a setup message to the MMS112, receives the media, transmits a teardown message to the MMS, andcommunicates with the NRP 110 prior to transmitting another setupmessage to the MMS to confirm that the MMS will provide the next mediaclip on the play script.

The examples for the Figures below may reference one or more of apublication by an owner, a distribution by the ESRP 104, a requestand/or selection by a viewer 118 or 120 processing a reservation requestby the RTSMS 106, a reservation made by the reservation system 108,communication between the RTSMS and the NRP 110, a request from the NRPto an MMS, an acknowledgement or denial of service by an MMS, acommunication from the NRP to the viewer denying or accepting apresentation streaming, and/or a subsequent session or connection fromthe viewer to the MMS. In the examples, reference to one or more ofthese actions may identify the embodiment as distributing, requesting,or providing media in accordance with a presentation embodiment or amedia clip embodiment described above. However, this discussion uses apresentation embodiment and a media clip embodiment for clarity andconciseness. It should be appreciated that any of the above statedembodiments, or any combinations thereof, may be used.

The streaming system 102 of FIG. 1 operates as follows. In a firstexample, a media owner generates a program with an order that is placedon the ESRP 104. The program has multiple media items, including a mediaclip for a movie and an advertisement. The program includes a timerestriction that it is not to be played between the hours of 7:00 p.m.and 9:00 p.m. Pacific Time. The program further includes a geographicrestriction requiring the program to be placed on a switch in thewestern region of the United States, including California.

The order for the program includes billing information, such as themedia owner is to be credited with 80% of the revenue generated from theprogram, and the network owner is to be credited with the remaining 20%.The media owner publishes the program with the respective order to theESRP 104.

The ESRP 104 processes the program with its respective media rules andorder. The ESRP 104 distributes the program to multiple switches in thewestern United States, including California. The ESRP 104 also transmitsto the RTSMS 106 the publication data, including an identification ofthe media clips in the program, the media rules, and the order.

A viewer 118 selects an option to obtain one or more programs which, forexample, contain movie media clips. In this example, the option is alink on the portal 116. When the link is selected, the portal 116 callsthe reservation system 108 on the RTSMS 106.

The reservation system 108 is notified that the viewer 118 requestedaccess to the program. The reservation system 108 determines that theprogram is active within the network. The order may request additionalviewer billing information, such as a credit card for a pay-per-viewevent or a subscription password to be supplied for billingauthorization. The reservation system 108 determines if the programcontains media rules that require a statistical identification of theviewer. If required by the media rules, the reservation system 108collects the statistical information.

The reservation system 108 creates a customized presentation for theviewer based on the program, including the play script of the mediaclips and the media rules, if any. The reservation system 108 builds areservation having the identification of the viewer 118 and theidentification of an NRP 110 selected to identify a switch to providethe presentation. In this example, the NRP identification is the hostname of the NRP 110. The reservation also includes the presentationidentification, including the customized play script of thepresentation. The customized play script includes media selected basedupon the statistical identification data, time of day, day of week,personal viewing preferences, or any other attributes that the publisherdeems pertinent. In this example, the presentation includes a moviemedia clip and an advertisement.

The reservation system 108 transmits the reservation to the NRP 110. Inaddition, the reservation system 108 transmits to the viewer 118 theplay script with each entry on the play script having the host name ofthe NRP, the reservation identification, and the presentationidentification.

The viewer 118 transmits a media locator request to the NRP 110. Themedia locator request in this example comprises at least one name on theplay script, the NRP host name, and the reservation identification.

The NRP 110 uses the received reservation identification to obtain thepresentation identification and additional data about the reservation.The NRP 110 processes the media locator request and the reservation datato determine if an MMS within the streaming system 102 can service therequest. The NRP 110 compiles a list of MMSs that have the program andthat can provide the presentation according to the media rules. In thisexample, the NRP 110 determines, based on load balancing factors andnetwork distribution rules, that the MMS 112 is the best selection toprovide the presentation.

The NRP 110 communicates with the MMS 112 to determine if the MMS canprovide the presentation. The MMS 112 responds that it can provide thepresentation to the viewer 118. In this example, the MMS 112 has astream caster that can stream the presentation to the viewer 118.

The NRP 110 transmits to the viewer 118 an IP address of a stream casteron the MMS 112. In addition, the NRP 110 transmits the reservation datato the MMS 112. Also, the NRP 110 saves information in a state modelidentifying the reservation identification, the presentationidentification, that the MMS 112 will stream the presentation to theviewer 118, and the time the MMS accepted the streaming request.

The viewer 118 receives the IP address and initiates a session with theMMS 112. The MMS 112 streams the presentation to the viewer 118,including the movie media clip and the advertisement. The MMS 112retains information in a state model identifying the reservationidentification, the presentation identification, the start and stoptimes of each media on the play script, and any viewing events, such asa pause, a forward, a reverse, or other events.

When each media on the play script has been streamed to the viewer 118,the viewer initiates an end to the session. The MMS 112 storesinformation in its state model identifying the end of the session. TheMMS 112 transmits its logs, SIB information, and state model informationto the RTSMS 106.

The MMS 112 notifies the NRP 110 that the presentation streaming iscomplete. The NRP 110 stores information in its state model identifyingthat the presentation streaming is complete and transmits the statemodel data to the RTSMS 106.

The RTSMS 106 processes the logs, the SIB information, and anyadditional data that originated from state models from both the NRP 110and the MMS 112. The RTSMS 106 collates the data using the reservationidentification to produce the MSDR data identifying billable events,including the presentation that was streamed to the viewer 118, theamount of media streamed to the viewer, and the streaming time.

The RTSMS 106 applies the order rules to the MSDRs. In this example, theRTSMS 106 produces a financial settlement and report identifying acredit of 80% of the revenue generated by the presentation to the mediaowner and a credit of 20% of the revenue generated by the presentationto the network owner.

In another example, the viewer 120 requests media and receives a playscript from the RTSMS 106 for viewing a presentation. The presentationhas three media clips. In addition, the NRP 110 receives thecorresponding reservation from the RTSMS 106. In this example, the MMS112 has two stream casters.

The viewer 120 transmits a request containing the reservationidentification to the NRP 110. The NRP 110 processes the request withthe reservation received from the RTSMS 106 to compile a list ofswitches that can provide the requested presentation. The NRP 110communicates with the MMS 112 to determine if the MMS can provide thepresentation to the viewer 120. The MMS 112 responds to the NRP 110 thatit has a stream caster that can stream the presentation to the viewer120. The NRP 110 transmits an IP address of the first stream caster onthe MMS 112 to the viewer 120.

The viewer 120 initiates a session with the first stream caster on theMMS at the IP address provided by the NRP 110. In addition, the MMS 112notifies the NRP 110 that the streaming session has been initiated. TheMMS 112 stores all information regarding the streaming and the statemodel.

The NRP 110 stores information in a state model identifying the MMS 112as providing the presentation. This information is transmitted in an NRPevent log to the RTSMS 106 as it occurs or at a specified configurabletime. In this example, the NRP 110 transmits the NRP log to the RTSMS106 every five minutes. In other examples, the NRP 110 can be configuredto transmit the NRP log to the RTSMS when a session is initiated betweena viewer and a particular switch and when that session is terminated. Inaddition, in other examples the NRP 110 can be configured to transmitthe NRP log at other configurable times or at different configurableevents.

When the session is initiated between the viewer 120 and the MMS 112,the MMS creates an SIB and subsequently transmits the SIB to the RTSMS106. In addition, while the media is streamed from the MMS 112 to theviewer 120, an SIB is created and transmitted to the RTSMS 106 at aconfigurable time. In this example, the configurable time is every fiveminutes. In other examples, the time may be configured to differentperiods of duration. In addition, in this example, the MMS 112 transmitsan SIB to the RTSMS 106 when viewing events occur, such as a stop, apause, a forward, or a rewind. Also, when the presentation streaming iscomplete and the session is terminated, the MMS 112 transmits an SIB tothe RTSMS 106.

When the session is complete and terminated, the MMS 112 notifies theNRP 110. The NRP 110 transmits a final NRP log to the RTSMS 106.

In this example, the RTSMS 106 collates all of the SIBs into an MSDRusing the reservation identification in each SIB. The MSDR then can beused to provide billing records to billing entities according to billingrules, such as those that may be in an order associated with theprogram. In other examples, the RTSMS 106 may use the NRP logs inconjunction with the SIBs to create the MSDR.

In another example, the viewer 118 receives a play script with areservation identification from the RTSMS 106. In addition, the NRP 110receives the reservation from the RTSMS 106. The viewer 118 transmits amedia locator request to the NRP 110, and the NRP 110 processes themedia locator request with the reservation data received from the RTSMS106. The NRP 110 compiles a list of switches, including the MMS 112,that can provide the presentation identified in the reservation. The NRP110 communicates in turn with the MMS 112 to determine if the MMS canprovide the presentation. The MMS 112 replies to the NRP 110 specifyingthat it can provide the presentation. The NRP 110 transmits an IPaddress of a stream caster on the MMS 112 to the viewer 118.

The viewer 118 initiates a session with the MMS 112. The MMS 112 streamsthe presentation to the viewer 118 as requested.

While the MMS 112 is streaming the presentation to the viewer 118, anerror occurs, and the MMS is not able to continue streaming thepresentation to the viewer. The MMS 112 notifies the NRP 110 that itcannot continue streaming the presentation to the viewer 118.

The NRP 110 determines that the session for the presentation must bere-routed and communicates with a second MMS identified on the list ofswitches capable of providing the presentation (not shown). The secondMMS notifies the NRP 110 that it can provide the presentation. The NRP110 notifies the first MMS 112 to route the session to the second MMS.

The session is routed to the second MMS. The second MMS provides therest of the presentation to the viewer 118. When the presentation hascompleted, the session is terminated by the viewer 118. The second MMSnotifies the NRP 110 that the streaming for the presentation is completeand the session is terminated.

In this example, the MMS 112 transmits SIBs to the RTSMS 106 when thesession is initiated, during the configurable periods of time while thepresentation is streaming, during any viewing events, when the streamcaster fails, and when the session is routed to the second MMS.Likewise, the second MMS transmits SIBs to the RTSMS 106 when thesession is routed to the second MMS and the second MMS starts streamingthe media for the presentation, during the configurable periods of timewhile the presentation is streaming, when any viewing events occur, andwhen the session is terminated. Each of the SIBs contains thereservation identification for the presentation. In addition, the NRP110 transmits NRP logs to the RTSMS 106 identifying both the MMS 112 andthe second MMS when the respective MMSs provide the media streaming forthe presentation.

The RTSMS 106 receives the SIBs from the MMS 112 and the second MMS. TheRTSMS 106 collates the SIBs to create an MSDR using the reservationidentification contained in each SIB. The MSDR then can be used forsettlement purposes.

In another example, the viewer 120 requests access to media. The RTSMS106 returns a play script to the viewer 120. The play script identifiestwo media clips, in addition to the reservation identification and theNRP identification. In this example, the media clips are identified byURLs, and the reservation identification is a reservation numberattached to the URL. Also, the NRP identification in this example is ahost name for the NRP 110. The RTSMS 106 also transmits the reservationto the NRP 110.

The viewer 120 transmits a request to the NRP 110. In this example, therequest is a media locator request. The media locator request identifiesthe play script and the reservation identification. The NRP 110processes the media locator request and the reservation received fromthe RTSMS 106. The NRP 110 compiles a list of all possible switches thatcan handle the presentation identified by the play script.

The NRP 110 communicates with the MMS 112 to determine if the MMS canprovide the presentation. The MMS 112 transmits a message back to theNRP 110 identifying that it can provide the presentation. The NRP 110transmits an IP address of a stream caster on the MMS 112 to the viewer120.

The viewer 120 initiates a session with the MMS 112. The MMS 112 streamsthe media for the first media clip identified on the play script to theviewer 120.

In this example, when the viewer 120 has received all of the media forthe first media clip, the viewer terminates the streaming session byinitiating a tear down message. This may occur, for example, when thenext media clip on the play script requires a different media servertype.

The viewer 120 determines that there is a second media clip of adifferent media server type on the play script for the presentation. Theviewer 120 contacts the NRP 110 to determine if a switch is able toprovide the second media clip for the presentation.

The NRP 110 communicates with the MMS 112 to determine if the MMS canprovide the second media clip on the play script for the presentation.The MMS 112 communicates back to the NRP 110 with a message stating thatthe MMS 112 cannot provide the second media clip on the play script forthe presentation because the MMS does not have the required mediaserver.

The NRP 110 receives the message from the first MMS 112. The NRP 110communicates with a second MMS (not shown) to determine if the secondMMS can provide the second media clip on the play script for thepresentation. The second MMS communicates a message to the NRP 110 thatit can provide the second media clip on the play script for thepresentation. The NRP 110 transmits a message to the viewer 120identifying an IP address of a stream caster on the second MMS.

The viewer 120 initiates a session with the second MMS at the identifiedIP address. The second MMS streams the second media clip in the playscript for the presentation to the viewer 120. When the streaming forthe second media clip is complete, the viewer 120 terminates thesession. The second MMS notifies the NRP 110 that the streaming for thesecond media clip is complete, and that the session is terminated.

The first MMS 112 and the second MMS transmit SIBs to the RTSMS 106 atthe initiation of each session, at the termination of each session, uponviewing events, and at configurable periods of time. In addition, theNRP 110 transmits NRP logs to the RTSMS 106. The SIBs and the NRP logsidentify the reservation identification for the presentation.

The RTSMS 106 collates the SIBs from each of the first MMS 112 and thesecond MMS to create an MSDR. The MSDR can be used for billing recordsand other settlement purposes.

FIG. 2 depicts an exemplary embodiment of a reservation system for astreaming system. The reservation system 122A comprises a service ordersystem 202, a financial screener 204, a presentation creator 206, and areservation generator 208. Systems and processes may be combined orseparated.

The service order system 202 identifies the viewer from which a requestis received. The service order system 202 authenticates the viewer 118or 120 to determine whether the viewer is authorized to make a requestfor the desired program. In one embodiment, the service order system 202compares the viewer profile against service rules provided by the mediaowner in the order. The service order system 202 may verify that theorder for the program is in effect and that the program is available ata viewing time requested by the viewer 118 or 120. In anotherembodiment, the service order system 202 may authorize any viewer 118 or120 and/or any request for a program. In this instance, a service rulerequiring validation may not be present or may provide that any viewermay receive the program. Other examples exist.

The service order system 202 may be configured to validate that arequest is received from a valid communication system, such as a validportal 116 of FIG. 1. In some embodiments, the validation of thecommunication system may not be required.

It will be appreciated that in other embodiments, authentication of theviewer 118 or 120 and/or validation of the communication systemproviding the request may involve external systems. For example, a mediaowner may make an arrangement with a portal site to allow viewing of allof the media owner's content on a fee for service basis where the portal116 owner pays the bill. No viewer identification or payment collectionis involved. When the request for service comes to the network owner,the service order system 202 can be defined to access the networkowner's accounts receivable system to determine if the portal 116 ismore than 90 days late in payment. If the portal 116 owner has not madea bill payment in the last 90 days, the service request can be rejected.

The financial screener 204 validates financial transactions with aviewer 118 or 120, such as by determining whether a viewer can pay for aprogram or whether a viewer has paid for a program, if payment isrequired from the viewer for a requested program. For example, afinancial transaction may be required for a pay-per-view program, asubscription, a gift certificate, discounted events, promotions, and/orcombinations of the above or other events.

In some embodiments, external systems may be used during a financialscreening process. For example, a viewer 118 or 120 requesting a pay-perview, non-subscription service may require an immediate credit cardpayment. In order for the viewer 118 or 120 to access the content, theviewer must provide valid credit card data that is passed to an externalcredit card processing system for payment authorization. If the creditcard processing system returns a credit accepted status, the viewer'stransaction continues to be processed. If the external credit cardapplication rejects the credit card, a message is forwarded to theviewer 118 or 120, and the viewer's transaction continues pending untila valid payment is made or the viewer cancels the request.

The presentation creator 206 creates a tailored presentation for aviewer 118 or 120 based upon the requested program and its associatedservice rules and settlement rules, if any. In some instances, thepresentation creator 206 may process the viewer profile, if the viewerprofile is available, with the viewer's request and the program rules togenerate the presentation. Thus, a presentation is customized for anindividual viewing session by the presentation creator 206.Additionally, in other embodiments, the presentation creator 206 mayreject a request instead of creating a presentation for the viewer 118or 120.

The presentation creator 206 may be configured to generate differentpresentations based upon different viewer profiles. For example,different advertisements may be selected for a presentation based upon aviewer profile. Alternately, a movie may have a different ending thatmay be selected for a different market, a different language, closedcaptioning, letter box format, or another selection.

The different selections for a media clip are based on a selectioncriteria provided by a media owner in the program, may specify directlywhich media clip to provide in the presentation, may provide a mediaalias that is resolved at a later time, including after a viewingsession has started, or provide another presentation criteria.Additionally, any portion of the presentation selection may be based onattributes and respective values identified for a viewer profile for aspecified program. The attributes may be demographics, such as age,gender, marital status, income, or other demographics, geographiclocation, such as a city, a state, a country, a college, a region, orother geographic location attributes, hobbies, such as basketball,tennis, rowing, crafts, or other hobbies for showing a productplacement, preferences, such as drama, comedy, religious preferences, orother preferences, job grades, such as enterprising, management, union,non-union, local law enforcement, or other job grades, and/or otherattributes for which a media owner identifies for a viewer profile.

The reservation generator 208 determines whether the streaming systemhas the necessary resources to stream a presentation for a requestedprogram to a viewer. The reservation generator 208 processes thepresentation generated by the presentation creator and the request toidentify whether a resource in the streaming system, such as a switch,can provide the presentation for a requested program and the generatedreservation. If the necessary resource or resources are not available tostream the presentation, the reservation generator 208 may reject therequest, put the request on a waiting list, or pass the request toanother system that may be able to provide the requested program, suchas to another RTSMS or an external system. If the reservation generator208 determines that the resources are available, the reservationgenerator may accept the request and create the reservation for thepresentation, including assigning a reservation identification to thereservation. The reservation generator 208 tracks the reservationidentification for each reservation.

The reservation generator 208 selects an NRP, such as the NRP 110, tohandle routing requests for the reservation and transmits thereservation to the selected NRP. The reservation may be transmitted tothe selected NRP at any time before the start time of the presentation,including immediately after the reservation is assigned to the viewerand the presentation, immediately prior to the assigned starting timefor the presentation, or anytime in between. The reservation generator208 creates a play script for the viewer and transmits the play scriptto the viewer. The reservation generator 208 creates a customized playscript for each customized presentation, including a play script for themedia clips in the presentation and the reservation identification. Inone embodiment, the play script contains one or more URLs, with each URLcontaining a media reference and the reservation identification. It willbe appreciated that the reservation may be for a single reservation fora viewer or part of a block of reservations. The single reservationand/or the block of reservations may be prior-established reservationsor future reservations.

FIG. 3 depicts an exemplary embodiment of an NRP of the presentinvention. The NRP 110A of FIG. 3 comprises an NRP control manager 302,a reservation cache 304, a name resolution system 306, a routing engine308, a switch manager 310, a media location cache 312, and an NRP LDSTS314.

The NRP control manager 302 monitors and stores the events and thestatus of each subsystem and device within the NRP 110A. The controlmanager 302 also monitors messages transferred between subsystems on theNRP 110A and processing of those messages by subsystems in the NRP. Thecontrol manager 302 generates an alarm upon detection of an error event.The control manager 302 also monitors and stores configuration changesmade from a network operator or another source. The control manager 302manages the NRP 110A at an aggregate level.

The control manager 302 maintains in memory the total bandwidth used bythe NRP 110A, the total number of active requests, the current not toexceed bandwidth capacity, the current not to exceed active requestscapacity, the current processing capacity, and the current not to exceedprocessing capacity. The memory enables the control manager 302 toreject name resolution requests, such as a DNS lookup request or abroadband SIP connection request, when the name resolution request willplace the NRP 110A above the desired thresholds.

The reservation cache 304 maintains reservations identifying current andimminent reservations in the streaming system 102. The reservation isused to feed the routing engine 308 and to validate whether areservation exists.

The name resolution system 306 is the entry point to the routing engine308. The name resolution system 306 receives the NRP identificationsignaling in a translatable protocol and provides the mapping back for areply. In one embodiment, the name resolution system 306 receives an NRPhost name in a DNS protocol format as the NRP identification and, afterthe routing engine 308 has processed the request and an MMS that canprovide the media is located, maps the response as an IP address to theMMS, a stream caster, or other device on the MMS. The name resolutionsystem 306 also resolves NRP identification requests from broadbandcommunication devices.

The name resolution system 306 manages communications with other NRPsand/or other signaling systems controlled by other networks. The latterusually requires conversion between various protocols.

The name resolution system 306 operates as a signal gateway and isconfigured to process in-band signaling or out-of-band signaling.In-band signaling is signaling that is contained within a transmissionpath of a streaming service. For example, the SIP protocol can bein-band signaling. Additionally, the real-time transport protocol (RTP)is configured to contain RTP control protocol (RTCP) data embeddedwithin the RTP transmission.

Out-of-band signaling is signaling that is transported via atransmission path separate from the media streaming path. The separatetransmission path may be via different physical links, via a differentinternet protocol (IP) port number on a same physical path, via avirtual private network (VPN), or another method transmitting data via aseparate logical or physical path.

The routing engine 308 determines whether to accept or to deny a requestfor media. If the routing engine 308 determines that an MMS can andshould provide the requested media, the routing engine will accept therequest. The routing engine 308 can reroute a media request. This canoccur, for example, if the stream caster or its media server on an MMSfails or otherwise cannot begin or continue streaming the requestedmedia. Other examples exist.

The routing engine 308 collects additional information for a connectionor a session based on how the connection or session is established overwhat is provided in the initial reservation. For example, if a viewer isconnecting via a directly managed broadband network, the routing engine308 collects detailed information on the actual logical virtualpath/virtual circuit. The routing engine 308 can update reservationinformation or NRP logs with this additional information and have theupdated information transferred to the RTSMS 106 for future use.

The switch manager 310 monitors and stores the state of the MMSs andtheir communication links. The switch manager 310 also transmits thereservation to the MMSs, receives requests from an MMS to reroute amedia stream, and responds to reroute requests.

The media location cache 312 caches program information, such as theidentification of the media in a program, on what MMS devices the mediais located, the anticipated streaming time of the media, the playingtime of streamed media, the average bandwidth needed to stream media ofa program, the maximum bandwidth needed to stream media of a program,and the quality of the media encoding. This program information is usedby the routing engine 308 to make routing decisions.

The NRP LDSTS 314 collects event data, such as state change data andreservation data, from other subsystems of the NRP 110A. The LDSTS 314transmits the event data, including NRP logs, to the RTSMS 106 forbilling, reporting, and network management.

FIG. 4 depicts an exemplary embodiment of an NRP control manager of thepresent invention. The control manager 302A of FIG. 4 comprises an alarmmanager 402, a load manager 404, and a reservation controller 406. Thealarm manager 402 operates with a process status storage element 408 anda signaling link status storage element 410. The load manager 404operates with the signal link status storage element 410, a manageddevices storage element 412, and a mirrored devices storage element 414.The reservation controller 406 operates with a reservation controlstorage element 416. The storage elements 408-416 each may be, forexample, a database, a table, an array, a programming object, a computerprocess monitoring event that can be called via an inter process orremote process communication, and/or another storage element. Forsimplicity, the storage elements 408-416 may be referred to asdatabases.

The alarm manager 402 operates to centrally control and monitor an NRP.The alarm manager 402 enables an operator to define one or more objectsfor the streaming system 102 that can be managed, for example, by simplenetwork management protocol (SNMP) or common management informationprotocol (CMIP). For example, an operator may define a managed objectfor network management of the streaming system 102.

Additionally, the alarm manager 402 enables an operator to define alertsthat may be unique to implementing the streaming system 102. Forexample, an alert may be defined by specifying the managed object and athreshold value for the managed object or an attribute of the managedobject. If the value of the managed object or the attribute exceeds,either by meeting, going below, or going above the threshold of themanaged object as specified by the threshold value, an alert may betriggered and generated to a console of the network operator and/or toan alarm log. For example, an invalid reservation identification countmay be specified for the NRP and measured every five minutes. If thecount reaches a specified number, such as ten, then an alarm may begenerated.

Also, the alarm manager 402 monitors signaling processes operating onthe NRP and generates an alert to a network operator and/or to an alarmlog as to a possible and/or actual degradation of service. Thesesignaling processes may be referred to as mission critical signalingprocesses. If a signaling process such as this halts, crashes, consumesan unreasonable amount of a resource, or otherwise causes an alertcondition, signaling processing may be halted. This may occur, forexample, where a name resolution system, such as the name resolutionsystem 306 of FIG. 3, temporarily halts. In this instance, reservationsthat were assigned to that NRP can no longer be routed by that NRP, anda secondary NRP will have to process current and future reservationsuntil the problem with the current NRP has been resolved. Reservationsthat already were routed may continue to be streamed.

The alarm manager 402 monitors the signaling processes and predictspotential and/or imminent failures. In some instances, the alarm manager402 may auto correct a detected problem. For example, the alarm manager402 may divert a reservation to another NRP and attempt to restart thename resolution system of the current NRP so as to restore the nameresolution system to full operation.

In one embodiment, the alarm manager 402 is configured to generateforecasts. In this embodiment, the alarm manager 402 is configured todetect whether a selected MMS is approaching its capacity or is overcapacity, even when the normal hardware SNMP device manager does notdetect an over capacity event. The alarm manager 402 may be configuredin this instant to determine the impact of scheduled reservations on theselected MMS and report if planned and current usage exceeds itscapacity. Forecasting provides an advantage, for example, whereforecasting of bandwidth use enables the streaming system to provide ahigh quality of service (QoS) for streaming high bandwidth, longduration media.

The alarm manager 402 monitors the data in the NRP process statusstorage element 408. The NRP process status storage element 408 containsthe current and past status and records from the internal NRP processes.The alarm manager 402 may be configured to alert an operator and/or analarm log if an internal NRP process is in an actual or potential alarmcondition. In another embodiment, the alarm manager 402 may beconfigured to detect if a routing engine, such as the routing engine 308of the NRP 110A (see FIG. 3), has halted. This may occur, for example,if routing software in the routing engine is not operating correctly. Inthis instance, the alarm manager 402 may be configured to alert anetwork operator and/or an alarm log to stop the routing engine and torestart the routing engine.

The alarm manager 402 also may be configured to monitor the signal linkstatus storage element 410. The signal link status storage element 410contains information identifying the current status and past records ofthe signal link transports for the signaling system 102. A signalinglink may be one link on a communication path between devices in thesignaling system 102, such as in an out-of-band signaling network. Asignaling link may be, for example, a virtual path/virtual circuitconnection, an IP connection, or another signaling link. The signalinglink status may be dependant on the technology used. Signaling linkstatus may include, for example, up/down, percent use, error rate, andother status attributes. The signaling link status may be accessed, forexample, by SNMP or CMIP.

The alarm manager 402 monitors the signaling links and records thestatus of each signaling link in the signaling link status storageelement 410. If a given signaling link is not operational, the alarmmanager 402 may be configured to alert a network operator and/or analarm log. The alarm manager 402 may be configured to attempt tore-establish a communication on the signaling link or establishcommunications to an alternate link to the same destination.

The alarm manager 402 also may be configured to enable a networkoperator to set attribute conditions, such as a signaling link loadlimit to ensure that signaling data is transported through the streamingsystem 102 on an efficient basis. The alarm manager 402 enables theoperator to set the load limit level from zero to one hundred percent.

The load manager 404 controls the use of one or more MMS devices thatare assigned to the primary control domain of that NRP. The primarycontrol domain of a selected NRP are those MMSs or MMS devices thatcommunicate with the selected NRP and that receive and followinstructions from the selected NRP, including instructions for streamingmedia to a viewer. The load manager 404 stores the status and statisticsof each MMS and MMS device in that NRP's primary control domain in themanaged devices storage element 412.

The load manager 404 also manages a secondary control domain set of MMSsand MMS devices. The secondary control domain includes one or more MMSsor MMS devices that are under the secondary control domain of anotherNRP. In the event the primary NRP for those devices fails, the loadmanager 404 of the current NRP will read the data located in themirrored devices storage element 414 to identify and control the devicesthat were assigned to the failed NRP. The load manager 404 will read thedata from the mirrored devices storage element 414 upon receiving aninstruction to service the secondary control domain.

The load manager 404 monitors the state model of each reservationaccepted by an MMS within its primary or secondary control domain. Theload manager 404 updates the state model and the streaming usestatistics and measures in the managed devices storage element 412.Examples of a streaming use statistic include the overall bandwidth useof an MMS, an individual streaming server bandwidth use within an MMS,an individual streaming server memory use, an individual streamingserver disk use, an individual streaming server signaling link use, andother statistics.

The load manager 404 may be configured to compute the available capacityof an MMS or an individual streaming server by media server type. Astreaming media server type may include Microsoft's Windows MediaServer, Real Server, Apple's Quick Time/Darwin server, Oracle VideoServer, and others. Available capacity may be classified over a timeperiod in configurable time increments, such as five minutes.Classifying available capacity over a time period reflects scheduledreservations that have not yet connected.

The reservation controller 406 operates with a reservation controlstorage element 416. The reservation controller 406 handlescommunications between one or more NRPs within the signaling system 102and communications to and/or from a signaling device of another packetnetwork to fulfill a reservation request. The reservation controller 406stores the reservation request and associated information wherenecessary in the reservation control storage element 416. Associatedinformation may include the destination to which the reservationcontroller 406 routed the reservation request, the time the reservationrequest was routed, and other data required to process the reservationrequest.

The reservation controller 406 maintains timers on remotely routedreservation requests and can cancel those reservation requests and/orreroute the reservation requests to another NRP or to a differentnetwork provider. The timers typically are kept for a reservationrequest forwarded to a destination NRP. The destination NRP is provideda configurable amount of time in which to respond to the reservationrequest with a positive or negative response. If the destination NRPdoes not respond within the allotted time, a different NRP may beselected to process the reservation request. However, if another NRPcannot be located, the reservation request may be refused.

The reservation request has a format referred to herein as thereservation format. The reservation format is used by one or moredevices within the NRP and/or one or more other devices within thesignaling system 102 to process the reservation request. In someinstances, external networks may or may not use the reservation formatused by the streaming system 102. Thus, in some instances, a messagereceived from an external network may require conversion to thereservation format. In other instances, a message to be transmitted toan external system may require conversion from the reservation format toa format receivable by that external network. Conversion may also berequired if two or more NRPs exist in the streaming system 102, and atleast one of the NRPs is operating a different version of software,firmware, and/or operating systems than the version used by one or moreother NRPs in the streaming system.

In those instances in which the format of the reservation requestrequires conversion, either between one or more devices within thestreaming system 102 or between a device within the streaming system anda device outside of the streaming system, the reservation controller 406controls converting the format of the reservation request between theone or more formats and/or other protocols. Examples of some signalingprotocols include the Internet Engineering Task Force (IETF) sessioninitiation protocol (SIP), the International Telecommunications Union(ITU) H.323, the World Wide Web Consortium (W3C) Extensible Hyper TextMarkup Language (XHTML), Extensive Markup Language (XML), and otherprotocols and private application interfaces.

FIG. 5 depicts an exemplary embodiment of a name resolution system. Thename resolution system 306A of FIG. 5 includes a signal authenticator502, a protocol identifier 504, and a protocol converter 506. The signalauthenticator 502 operates with a security authorization storage element508, the protocol identifier 504 operates with an active link protocolstorage element 510, and the protocol converter 506 operates with aprotocol conversion mapping storage element 512 and a protocolconversion library 514. The storage elements 508-514 each may be, forexample, a database, a table, an array, a programming object, a computerprocess monitoring event that can be called via an inter process orremote process communication, and/or another storage element. Forsimplicity, the storage elements 508-514 may be referred to asdatabases.

The signal authenticator 502 operates with the security authorizationstorage element 508. The signal authenticator 502 determines ifsignaling as received from various locations is valid. The signalauthenticator 502 uses data stored in the security authorization storageelement 508 to verify the validity of communications received within thestreaming system 102 and/or another network.

For example, the signal authenticator 502 may validate a communicationby identifying the IP address of the device sending the communicationand verifying that the sending IP address is valid, reading embeddedsecurity key data within the communication and validating the securitykey data, identifying physical device serial numbers and validating theserial numbers, identifying the signaling link as a secure link, and/orother security schemes. In another example, two internet serviceproviders (ISPs) may agree to transmit communications between theirnetworks. In this example, the security authorization storage element508 may contain the IP addresses of the devices of both networks and asecurity key to be used when processing communications from anothernetwork, and the signal authenticator 502 will validate thecommunications.

The signal authenticator 502 may receive and process a communication,identify the sending IP address and a security key, and use a processand/or lookup to the security authorization storage element 508 toidentify whether the IP address is listed in the security authorizationstorage element, to decode the security key, and to match the decodedsecurity key to validate the information identified in the securityauthorization storage element. In another example, the securityauthorization storage element 508 may be configured as a cache ofrecently used security keys. In this example, the signal authenticator502 may be configured to access a public key data store or certificateverification service to validate a security key.

In addition to the information identified above, the securityauthorization storage element 508 also may contain data identifyingsignaling network points including signaling end-points, the companythat owns the signaling network point, contact information identifyingthe manager of the signaling network point, and/or other data. Asignaling network point is a device that is addressable from a signalingstandpoint. A signaling end-point identifies a signaling network pointthat is at one end of a communication.

The protocol identifier 504 operates in conjunction with the active linkprotocol storage element 510. The protocol identifier 504 maintains alist of active signaling links and information used to communicateservices on each link. The protocol identifier 504 stores the signalinglink information in the active link protocol storage element 510.Signaling link information may include whether the signaling link usesin-band or out-of-band signaling, protocols that may be used on or withthe signaling link, what signaling links may be used as back-upsignaling links to a signaling network point, including a signalingend-point, whether the signaling link is not operational and the reasontherefore, whether the signaling link is active, the desired not toexceed link load limits, signaling link prioritization to a givensignaling network point, a transport type, and other data useful formanaging signaling links and communication paths.

The protocol converter 506 operates in conjunction with the protocolconversion mapping storage element 512 and the protocol conversionlibrary 514. The protocol converter 506 converts communications betweenthe reservation format and other protocols, as explained more completelyabove with respect to FIG. 4. The protocol converter 506 obtainsprotocol information from the protocol conversion mapping storageelement 512, such as by identifying data elements and other protocolelements for the SIP protocol. The protocol converter 506 then can mapdata elements from the reservation format to the desired protocol. Theprotocol conversion mapping storage element 512 contains protocolidentifiers for mapping protocols that have similar attributes as thereservation format, but different formatting and naming conventions.

If the conversion between the reservation format and anther protocolrequires more than a simple mapping, the protocol converter 506 callsroutines stored in the protocol conversion library 514. These routinestypically define application programming interfaces (APIs) using an openstandard, such as XHTML, XML, or another standard. APIs normally arenegotiated between networks and may be considered signaling networkpoint specific. For example, protocol conversions may be required for arouting request made on the ingress side, for a communication to theforwarding protocol, for a communication from a forwarding reply, and/orfor a communication returning the results of a routing request on theegress side.

The routines in the protocol conversion library 514 may be configured todetermine the protocol to be used for converting the communication andto then perform the conversion. If the protocol conversion library 514does not contain data for the received communication, the protocolconversion library 514 and the protocol converter 506 may be configuredto default to a native protocol of the streaming system 102, such as thereservation format.

FIG. 6 depicts an exemplary embodiment of a routing process for arouting engine. The routing engine 308A of FIG. 6 depicts a logicaldefault process for routing media. However, other default processes mayexist.

The routing engine 308A locates one or more MMSs and/or MMS devices thathave the requested media identified by a reservation request at step602. For example, the routing engine 308A may locate those MMSs thatcontain 100% of the media identified for a requested reservation. Inanother example, the routing engine 308A may be configured to locate theMMSs that contain the first media item to be viewed for a requestedreservation and the presentation generated therefore, and subsequentmedia items requested in the reservation (and to be generated for thepresentation) are transported to the selected MMS while the viewerreceives the first media item.

At step 604, the routing engine 308A determines if the MMSs thatcontained the requested media have the capacity to stream the media tothe viewer. The capacity is measured in current usage and futurescheduled usage. For example, a viewer may request a two hour movie tobe generated in the moving pictures experts group (MPEG) formatrequiring 4 megabytes of constant bandwidth. The routing engine 308Adetermines if the MMS currently has 4 megabytes of bandwidth, theappropriate processing capacity, and other capacity items.

The routing engine 308A also reviews future scheduled activity andforecasts the impact of the future scheduled activity on the capacitymeasures. In one embodiment, the routing engine 308A also may beconfigured to then generate an overall weighted average rating theability of each MMS to stream the requested media. In one example, theMMSs scheduled to be used heavily in a live broadcast of a future eventare ranked lower than the MMSs that are not transmitting the livebroadcast of a future event.

At step 606, the routing engine 308A matches the selected MMSs to thestreaming service configuration. As used in this paragraph, thestreaming service configuration is identified by the networkdistribution rules and, in some instances, rules identified in an orderof a program (hereafter, “program rules”). The routing engine 308A thenprioritizes the MMSs that meet the network distribution rules and theprogram rules to determine the order in which the MMSs may be contactedto locate an MMS that can service the reservation request.

For example, a routing preference of next-sequential may prioritize alist of MMSs based upon what MMS last serviced a reservation request. Inthis example, a streaming system 102 may have seven MMSs. If a previousreservation request was serviced by MMS 4, then the current reservationwill be serviced by the next available MMS greater than MMS 4 that canhandle the reservation (i.e. the presentation generated for thereservation request). For example, MMS 5 does not have the requiredmedia requested, and MMS 6 contains all of the required media but doesnot have available capacity. Additionally, MMS 7 contains all of therequired media and has the capacity available to stream the media. Inthis example, MMS 7 is the next available MMS greater than MMS 4. Thus,MMS 7 is prioritized to the top of the routing list. This prioritizationin routing is referred to herein as next-sequential routing.

In another example, the streaming system 102 may be configured to usemost-idle routing, thereby selecting the most-idle MMS. In this example,the list of available MMS devices that are configured to service therequested media are prioritized in order of the MMSs that have the leastcurrent and planned activity.

In another example, the routing engine 308A is configured to enablebumping for the routing process and identifies the precedents to begiven to other networks over bumping. Bumping refers to a reservationrequest or other message being bumped for another reservation request ormessage. Bumping may be based on network owner policy. For example, aper-per-view viewer might have priority over a non-paying viewer. Arevenue producing stream might have priority over a test stream. Acompany/publisher might agree to have a lower priority to obtain a lowerrate. Priorities might be agreed to in a service order. Emergency-basedstreams might have priority over normal streams. Other examples exist.

In still another example, program rules may be entered by a media owner.However, the network owner may override the program rules if the programrules violate or are inconsistent with contractual provisions agreedupon by the parties or network distribution rules. In yet anotherexample, a media owner may need to change a program rule but is not ableto physically connect to the streaming system 102 to make the programrule change. In this example, the media owner may request the networkowner to directly enter the program rule, thereby overriding routingaccording to that program rule. Other examples exist.

Thus, the routing engine 308A identifies the MMSs that can servicerequested media for a presentation at step 606. The routing engine 308Aidentifies these MMSs based on which MMSs have the media and thecapacity and provides a selection probability based on the selectedconfiguration according to the network distribution rules and theprogram rules.

At step 608, the routing engine 308A generates an overall sorted listfrom 1 to N of the MMSs that can generate the requested media to theviewer. The sorted list may, for example, be based on the selectionprobability determined at step 606. The routing engine 308A may apply aweighted average algorithm, such as the location of each MMS withrespect to the viewer, the relative capacity of each MMS, includingcurrent and planned capacity, contractual factors, and/or other selectedfactors. The sorted list then may be used to communicate with each MMSaccording to the listed prioritization to ensure that at least one MMSmay stream the requested media to the viewer. If the first MMS on thelist rejects the request, the second MMS on the list is contacted and soon. This process continues until at least one MMS accepts thereservation or until a treatment process is applied to the reservationrequest. A treatment process identifies a reason and a result forabnormal routing of a reservation request or some other signaling orcommunication. The treatment processes are described more completelybelow.

FIG. 7 depicts an exemplary embodiment of a switch manager. The switchmanager 310A of FIG. 7 comprises a switch configuration manager 702, astreaming service configuration manager 704, a bandwidth manager 706,and a route latency manager 708.

The switch configuration manager 702 operates with a switchconfiguration storage element 710. The streaming service configurationmanager 704 primarily operates with a streaming service configuration(config) storage element 712 and an active load storage element 714.Secondarily, the streaming service configuration manager 704 may operatewith a current bandwidth use storage element 716 and a scheduledbandwidth use storage element 718. The bandwidth manager 706 operateswith the current bandwidth use storage element 716 and the scheduledbandwidth use storage element 718. The storage elements 710-718 each maybe, for example, a database, a table, an array, a programming object, acomputer process monitoring event that can be called via an interprocess or remote process communication, and/or another storage element.For simplicity, the storage elements 710-718 may be referred to asdatabases.

The switch configuration manager 702 operates with the switchconfiguration storage element 710 to store and retrieve configurationdata for one or more MMSs. The switch configuration manager 702 usesSNMP and CMIP management information base (MIB) objects and/or processesto determine the hardware configuration of one or more MMSs and/or MMSdevices. The hardware configuration data is stored in the switchconfiguration storage element 710 and is viewable from the RTSMS 106(see FIG. 1) for authorized users.

The switch configuration manager 702 uses the MIBs to determine if theMMS and/or the MMS devices are available for use, are in an alarm state,are otherwise awaiting repair, and/or are in a maintenance state forwhich the MMS or the MMS equipment is unavailable for use. The switchconfiguration manager 702 stores the configuration data in the switchconfiguration storage element 710 for each event that causes a statechange in the equipment status or a service impairment status.

The streaming service configuration manager 704 stores and accesses datain the streaming service configuration storage element 712 and theactive load storage element 714. The streaming service configurationmanager 704 also accesses data in the current bandwidth use storageelement 716 and the scheduled bandwidth use storage element 718.

The steaming service configuration manager 704 enables authorized usersto view and update routing data and tables, such as the routing tablesidentified in FIGS. 8-11. The streaming service configuration storageelement 712 contains data identifying network distribution rules, suchas for how media should be routed for the entire streaming system 102,data used to control a group of MMSs, data used to determine switchprioritization to determine a list of MMSs that can provide requestedmedia to a viewer, and other data.

For example, a sort algorithm in the streaming service configurationmanager 704 may be set to next-sequential switch, least idle switch,most idle switch, switch closest to the viewer, lowest transportlatency, and other approaches. In each instance, the streaming serviceconfiguration manager 704 reads the sort algorithm setting and theassociated routing processing data from the streaming serviceconfiguration storage element 712.

In another example, an algorithm is set to stream media from a switchthat is the closest point of service to the viewer. In still anotherexample, a network owner may select a transport path that has the lowesttransport latency through the streaming system. This switch may notnecessarily be the closest switch. Transport latency is the time betweenwhen a transport communication/message is sent from a first device andwhen the communication/message is received at another device.

The streaming service configuration storage element 712 also maintainsdata identifying load factors for the streaming system 102 as a whole.The load factor data is used by the streaming service configurationmanager 704 to monitor the collective load and to prevent the streamingsystem 102 or an individual MMS from being overloaded.

For example, the streaming service configuration manager 704 may beconfigured to randomly reject reservation requests when the streamingsystem 102 is 80% currently used. In this example, once the 80%threshold is reached, a selected random rejection rate, such as 40%, maybe specified so that 40% of the new reservation requests are rejectedwhile the streaming system 102 remains at 80% capacity. In this manner,the quality of service may be maintained for those viewers alreadyconnected to the streaming system 102. Additionally, the streamingservice configuration manager 704 uses the streaming serviceconfiguration storage element 712 data to establish and maintainreal-time stream controls and pre-established stream controls.

The active load storage element 714 contains data identifying the mediaserver types operating on respective MMSs. For example, a media servermay be a Microsoft Windows Media Server, an Apple Darwin Server, a RealNetwork Real Time Server, an Oracle Video Server, or another type ofmedia server. For each media server, the active load storage element 714may contain media server type, current media server status, activationstart time, planned media server termination time, media server softwarecapacity settings, media server version number, media server logsettings, media server publication points for content, content filetypes the media server can process, and other data relevant to supplyingstreaming service. The streaming service configuration manager 704 alsostores current streaming capacity for the media server type andidentifies the time and date when changes are to be made to a mediaserver, such as hardware or software upgrades, maintenance, or otherservice impairment events.

The bandwidth manager 706 monitors bandwidth use and forecasts neededbandwidth based on scheduled reservations. The bandwidth manager 706 mayobtain information for future reservations, thereby identifyingscheduled bandwidth use, from the scheduled bandwidth use storageelement 718.

The bandwidth manager 706 accesses current streaming information fromthe state model to determine bandwidth currently being used. Thebandwidth manager 706 also communicates with the streaming serviceconfiguration manager 704 to determine the current available capacity.The bandwidth manager 706 then generates a rolling forecast of bandwidthuse and stores that bandwidth use forecast data in the current bandwidthuse storage element 716. For example, the bandwidth manager 706 mayidentify bandwidth currently being used and identify forecastedbandwidth use based on requested and/or to be processed reservations.The bandwidth manager 706 may use this data to forecast for configurableperiods of time, such as 4 hours, 24 hours, 48 hours, 5 days, or anotherforecast range. The bandwidth manager 706 will update the rollingforecast as additional data becomes available, such as actual bandwidthuse and/or additional requested and/or accepted reservations.

The bandwidth manager 706 also may forecast the bandwidth use for eachMMS based on a transport traffic pattern. A transport traffic pattern isused to measure each segment of a specified signaling link, transportpath, device, and/or another segment, to determine bandwidth use so thatend-to-end bandwidth use may be measured. Once usage patterns andbottlenecks are recognized, optimizations can be implemented to improveperformance and bandwidth use. For example, the number of IP routelocations, from a designated MMS to a desired end point are required toreach that end point. To fully identify the transport traffic pattern,the bandwidth manager 706 also may identify the millisecond delay tothat location, the start/end forecast time for the pattern, actual testresults recorded during the identified time period, the designation ofone or more IP address types, such as a full IP address, a part of aCIDR block, and/or other transport traffic pattern attributes.

The route latency manager 708 executes tests between a selected MMS anda pre-determined network point. The route latency manager 708 mayexecute a test on an on-going, periodic, or one time basis and providethat information to the bandwidth manager 706. The route latency manager708 may be configured to execute tests on a packet based transport, suchas TCP/IP, ATM, frame relay, and other packet based transports. In oneembodiment, the route latency manager 708 executes a test to process aTCP/IP ping and trace route command to each TCP/IP address that made aconnection or session to a specific MMS in a configurable period oftime, such as 24 weeks. In another example, the route latency manager708 executes a TCP/IP ping and trace route test to each viewer that is amember of a subscription service. The test may be based upon theviewer's full IP address.

FIG. 8 depicts an exemplary embodiment of a data structure used by anNRP to execute a state machine. The data structure is comprised as aseries of tables that point to one another in various ways. The pointersmay have a next function and next partition designation. The nextfunction points to a next routing process, and the next partition pointsto an entry or a range of entries in the tables used for that process.While the pointers for an exemplary media processing are illustrated inFIG. 8, other examples exist. The routing data structure 802 embodimentof FIG. 8 depicts an active reservations table 804, a network accesstable 806, a signal mapping table 808, a signal access point table 810,a stream control table 812, a treatment table 814, a referring hosttable 816, an exception table 818, a personal identification number(PIN) table 820, a content screening table 822, a content location table824, a network status table 826, a day of year table 828, a day of weektable 830, a time of day table 832, a signal route choice table 834, anda class of service table 836.

FIG. 8 depicts one embodiment in which a reservation request flowsthrough the tables of the data structure between incoming access of thereservation request through the outgoing access in which a reply istransmitted to the viewer.

The routing data structure 802 is depicted as flowing from tables in anincoming access group 838 to an incoming access control group 840.Routing then passes through a switch identification group 842 to anoutgoing access control group 844. In the example of FIG. 8, the routingnext flows through an outgoing access group 846. It will be appreciatedthat FIG. 8 depicts an exemplary embodiment in which tables for therouting data structure 802 are grouped for one exemplary routing. Inother examples the tables of the routing data structure 802 may begrouped differently, one or more of the tables depicted in FIG. 8 maynot be used on a particular routing, or all of the tables depicted inFIG. 8 may be used for the particular routing.

In the embodiment of FIG. 8, the incoming access group 838 receivesreservations from the RTSMS 106 at the active reservations table 804.The network access table 806 receives the reservation request from theviewer. Signal mapping data from the signal mapping table 808 andreservation and viewer information from the network access table 806passes through to the signal access point table 810. Active reservationdata from the active reservations table 804 may pass to the streamcontrol table 812. Additionally treatment information may pass from thetreatment table 814 to the signal access point 810.

As a default, routing then is transmitted to the referring host table816 in the switch identification group 842. Following, routing may passthrough the exception table 818, the personal identification (PIN) table820, the content screening table 822, the content location table 824,and to the network status table 826. In some instances, routing may thenpass through time and date tables, such as the day view table 828, theday of week table 830, and the time of day table 832. Routing may passfrom any of the network status table 826, the day view table 828, theday of week table 830, and the time of day table 832 to the signal routechoice table 834 of the outgoing access control group 844.

The outgoing access control group 844 generally formulates informationfor a reply to the viewer. From the signal route choice table 834,routing may pass to the class of service table 836, to the signal accesspoint table 810. Treatment information may be received from thetreatment table 814 at the signal access point 810. Additionally, signalmapping data from the signal mapping table 808 may be received at thesignal access point table 810.

The signal access point table 810 then routes reply data through thenetwork access table 806 of the outgoing access group 846 to betransmitted to the viewer. Additionally, reservation data may betransmitted from the signal access point 810 to the active reservationstable 804 of the outgoing access group 846 to be transmitted ontoanother network device or to another device in the streaming system 102.

It will be appreciated that the routing identified in FIG. 8 is anexemplary embodiment. Other examples exist.

The active reservations table 804 contains information required to map apresentation to an executable play script that will be processed by anMMS. Each reservation generated by the reservation system 108 of theRTSMS 106 (see FIG. 1) has an entry in the active reservations table804. Each reservation request that has not fully executed or cancelledis depicted in the active reservation table 804.

The network access table 806 contains information used to provide thepublic transportation side of a connection or a session. The publictransportation side typically refers to a part of the streaming system102 or another network that is available to viewers that are not on aprivate, out-of-band signaling network. Typically, one record appears inthe network access table 806 for each network access adapter that canstream media found on an MMS. A network access adapter typically refersto the hardware that connects a media server in an MMS to the rest ofthe streaming system 102 or to another media server in another network.

The network access table 806 also can be configured to hold records forprivate network access adapters, and the routing data structure 802 alsocan be configured for private network access adapters. The networkaccess table 806 typically is accessed from the signal access pointtable 808, the signal route choice table 834, or an external mediarouting process via an internal routing process that controls mediarouting to and/or from an external network.

The signal mapping table 808 enables the NRP to decode incomingsignaling messages from protocols other than the reservation format intothe reservation format for processing by the NRP. The signal mappingtable 808 also enables the NRP to alter formatting for outgoingsignaling messages from the reservation format to a protocol required tobe received by the destination device. When the incoming signal recordis converted to the common reservation format, a signal decode messagemapping type is used as a key to the signal mapping table. When anoutgoing signaling record is converted from the reservation format toanother format, a signal encode message mapping type is used as the keyto the signal mapping table 808.

The signal mapping table 808 contains information and rules identifyingthe attribute names from the reservation format and how they are mappedto and from attribute data of the desired protocol to which it will beconverted or from which the message will be converted. The signalmapping table 808 also identifies programming libraries that are to becalled for the data conversion.

The signal access point table 810 contains information used to identifysignaling network points and data links. The signal access point table810 also contains information related to devices from which areservation can originate, such as from a network security standpoint,devices to which the reservation request can be routed, such as from anetwork security and capacity/availability standpoint. The signal accesspoint table 810 also contains information identifying signalingprotocols used to communicate with other signaling network points. Thesignal access point table 810 may point to any switch identificationgroup 842 table, the class of service table 836, the signal mappingtable 808, the stream control table 812, and the signal route choicetable 834.

The stream control table 812 enables the NRP to manage network overloadconditions without fully processing a reservation request. This preventsthe NRP and the MMS from shutting down fully and not providing serviceat all. A network/streaming system overload condition may occur when allavailable resources in a device nears capacity. For example, in theevent of a disaster, there may be a spike in viewer interest for aparticular piece of news footage of the event. The number of results andrequests may cause the MMS to fail thereby causing everyone currentlyviewing any media to be disconnected and causing all new reservationrequests to be rejected.

The stream control table 812 enables a network owner to throttlereservation requests, thereby maintaining service to viewers currentlyconnected. The stream control table 812 further enables a network ownerto reject a portion of new reservation requests with minimal NRPresources needed. The amount by which reservations may be throttled isconfigurable.

The treatment table 814 contains information identifying protocolerrors, network operation errors, and other events identifying why astreaming service is not provided. The treatment table 814 may identifythe reason for the error and provide the reason to the viewer with anadequate explanation of the error. For example, if a reservation requestidentifies media requiring an access code, but the access code is notprovided within the reservation or a subsequent communication, thereservation request will be sent to the treatment table 814 causing amessage to be generated to the viewer that the code has not been enteredor is incorrect.

The treatment table 814 identifies special actions to be taken in thecourse of processing a reservation request. For example, a cableoperator may want to stream a media clip for a message stating thattheir video-on-demand ordering system is not operational because ofmaintenance, instead of sending a text error message to the set top boxto be displayed on the viewer's television. In another example, thetreatment table 814 might be accessed from the PIN table 820 to blockmedia that contains unacceptable subject matter. The owner of the settop box could request that specific media be blocked from the set topbox in the living room, but allowed to be viewed on the set top box inanother room. In this instance, the set top box identification is usedin the PIN table 820 to treat the living room set top box with a videomessage stating that the customer has forbidden this material to bedisplayed via that particular set top box.

The referring host table 816 contains information identifying routingfor a reservation request based on which entity referred the reservationrequest to the streaming system 102. For example, an internet basedreservation request may use a URL of the hypertext transfer protocol(HTTP). The URL may contain the name of the referring web portal. Anagreement between the web portal owner and the network owner of thestreaming system 102 may require routing to a specific MMS, to anotherdevice, or other specific routing instructions. The referring host table816 typically defaults to the exception table 818. Although, thereferring host table 812 may point to other tables.

The exception table 818 is used to identify various exception conditionsrelated to the reservation request. The exception conditions mayinfluence the routing or handling of media identified in the reservationrequest. A reservation request may be screened resulting in the routingtaking a different path through the routing data structure 802. This mayoccur based on multiple factors, such as a special contractual agreementbetween one or more of a viewer, a network owner, another network owner,a media owner, and/or another entity. For example, if a reservationrequest is an internet originated request coming from a specific party,special routing directly to a specified MMS may be required.

The exception table 818 contains information enabling a reservationrequest to be specially handled, that is screened, based, at least inpart, on the identification of the originating network owner. Theidentification of the originating network owner may be determined from afull or partial IP address, the viewer's media player software versioninformation, and/or access network packet type information, such as ATM,frame relay, cable, and/or IP. The exception table 818 typicallydefaults to the PIN table 820. Although, the exception table 818 alsomay point to any other switch identification group 842 table, the signalroute choice table 834, or the class of service table 836.

The PIN table 820 is used to identify any special characteristics orrequirements related to a viewer, such as a protocol required tocommunicate to the viewer's media player, screening required to blockfraudulent account use, default time zone information, content ratingblocking, and other characteristics. The PIN table 820 can identify asingle viewer or a group of viewers, and the identified viewercharacteristics may be configurable by the network operator. The PINtable 820 typically defaults to the content screening table 822.Although, the PIN table 820 may point to any other switch identificationgroup 842 table, the signal route choice table 834, and the signalmapping table 808.

The content screening table 822 is used to screen a program orindividual media during a routing process. A media owner may place mediaon the streaming system 102 that the network owner does not desire orthat violates or is inconsistent with an agreement with the networkowner. The content screening table 822 contains information that enablesthe media to be screened for those undesirable or inconsistentattributes. The content screening table 822 contains media information,such as a program identification, media identification, media formattype, media rating type, agreement based information, and other datagenerated by the ESRP 106. The content screening table 822 enables anetwork owner to override instructions of a media owner located in aprogram. The content screening table 822 typically defaults to thecontent location table 824. Although, the content screening table 822may point to any other switch identification group 842 table and thetreatment table 814.

The content location table 824 identifies the media located at specificMMSs within the streaming system 102 or in another streaming network.The content location table 824 contains information identifying media,such as a maximum transmission bandwidth required, an estimated playtime of the media, a digital media file size, a content rating, andother media information. The content location table 824 typicallydefaults to the network status table 826. Although, the content locationtable can point to any other switch identification group 842 table andthe treatment table 814.

The network status table 826 determines the current MMS capacityavailable and the transport latency from each MMS to one or more viewerlocations. The network status table 826 may contain network information,such as current usage of a processor of an MMS, available and used mediastorage, in-use and planned bandwidth, and in-use and planned mediatransport. The network status table 826 also identifies capacity. Thecapacity is adjusted for any hardware failures that currently are openand that impact media distribution to viewers. The network status table826 typically defaults to the signal route choice table 834. Although,the network status table 826 also may point to any other switchidentification group 842 table and the treatment table 814.

The day of year table 828 contains information that causes media orprograms to be routed differently based on the day of the year. The dayof the year table 828 typically defaults to the signal route choicetable 834. Although, the day of year table 828 also may point to anyother switch identification group 842 table or the treatment table 814.

The day of week table 830 contains information that causes media orprograms to be routed differently based on the day of the week. The dayof the week table 830 typically defaults to the signal route choicetable 834. Although, the day of week table 830 also can point to anyother switch identification group 842 table and the treatment table 814.

The time of day table 832 contains information that causes media orprograms to be routed differently based on the time of day. The time ofday table typically points to the signal route choice table 834. Thetime of day table also may point to any other switch identificationgroup 842 table and the treatment table 814.

The signal route choice table 834 identifies alternative signal accesspoints that may be used to complete a reservation request. The signalroute choice table 834 identifies one or more NRPs within the streamingsystem 102 and/or another network that are interconnected to each otherand/or other networks.

The signal route choice table 834 may select a secondary NRP, forexample, when a first selected NRP cannot process a reservation requestbecause all of the MMSs that the first NRP controls are busy. Thus, if afirst NRP cannot service a reservation request, such as when all MMSsfor which the NRP has primary control are not able to process thereservation request, the signal route choice table 834 may selectanother NRP and/or MMS. The signal route choice table 834 typicallypoints to the treatment table 814 or the signal access point table 810.Although, the signal route choice table 834 may point to the class ofservice table 836, the signal mapping table 808, the stream controltable 812, and other tables.

The class of service table 836 identifies protocols that are notcompatible with each other. The class of service table 836 may beaccessed using a class of service partition code provided by the signalaccess point table 810. The class of service partition code typically isrequired from the access point records for both the originatingsignaling network point and the terminating signaling network point. Ifthe protocols on the two signaling network points are incompatible, theclass of service table 836 typically will point to the signal routechoice table 834, thereby enabling another terminating signaling networkpoint to be selected. Although, the class of service table 836 may pointto the treatment table 814, the exception table 818, and other tables.

An initial reservation request typically is processed by the activereservations table 804. The active reservations table 804 points to thesignal access point table 810 or the stream control table 812. Thesignal access point table 810 will identify if the reservation data isbeing received from a valid source, if signaling is in-band orout-of-band, identify the network owner of the sending signaling networkpoint, the signaling protocol type, and other information about thesignaling network point sending the reservation request. The statemachine described above and the routing data structure 802 uses thisinformation to decode the reservation request and the signaling datareceived. Typically, the decoding is completed in the signal mappingtable 808 and the network access table 806. Once the reservationrequest, the originating signaling network point, and the originatingtransport network are determined and recorded, the next default table tobe accessed is the referring host table 816.

FIG. 9 depicts an exemplary embodiment of a stream control table 812A.The stream control table 812A of FIG. 9 comprises a stream percentskipped table 902 and a stream rate table 904. The stream percentskipped table 902 and the stream rate table 904 are used to control thenumber of reservation attempts made on the streaming system 102 or anindividual MMS within the streaming system.

The stream percent skipped table 902 is used to control streamedconnection attempts based on a percent value of the traffic that isprocessed through the state machine. The stream percent skipped table902 typically defaults to the signal access point table 810 or thetreatment table 814.

The stream rate table 904 is used to control stream attempts on anattempt per second basis. Preferably, attempts within a range of 100 persecond to 1 per minute are programmable. Although, ranges above andbelow that are configurable. The stream rate table 904 typicallydefaults to the signal access point table 810 or the treatment table814.

FIG. 10 depicts an exemplary embodiment of a network status table 826A.The network status table 826A of FIG. 10 comprises a switch equipmentstatus table 1002, a signal network status table 1004, a public networkstatus table 1006, and a transport latency table 1008. It will beappreciated that other tables may be included in other embodiments ofthe network status table 826A.

The switch equipment status table 1002 identifies components within eachMMS that are used to supply streaming and signaling services to one ormore network devices, such as to one or more viewers. The switchequipment status data may be collected via a common systems managementapproach, such as SNMP, CMIP/CMISE, or a vendor specific managementsystem. The switch equipment status may be collected by a managementsystem, such as the RTSMS 106 (see FIG. 1), and transmitted to the NRP110 for storage in the switch management status table 1002 and othertables where necessary. Switch equipment status data may include, forexample, disk size, order numbers, media file names and sizes, switchidentification numbers, and/or other media and/or switch attributes.

The signal network status table 1004 identifies packet signaling andtransport links and devices. For example, a signaling link may be IPbased communicating via an ethernet card in a computer. The ethernetcard and its status would be identified in the signal network statustable 1004. Also identified would be the status of other signalingnetwork points and their devices. For example, a signaling network pointmay be unavailable due to maintenance activity. The inactive status ofthe signaling network point will be identified in the signal networkstatus table 1004.

The public network status table 1006 identifies packet routing devicesthat are within a physical facility in which the MMS is located, but arenot solely dedicated for use by the MMS. For example, an MMS may beinstalled at an ISP location, which would require all IP requests to berouted through the ISP's routing equipment. This equipment may be usedby multiple services at the ISP site. In this example, the publicnetwork status table 1006 identifies the service status of thisequipment, including any degradation of service status for theequipment. The data identified in the public network status table 1006may be obtained, for example, via a common systems management approach,such as SNMP, CMIP/CMISE, specific test routines contained within anMMS, and other methods.

The transport latency table 1008 identifies data for latency between anMMS and various points within the streaming system 102 or another packetnetwork. The latency data may be created and/or obtained by one or moreMMSs and forwarded to the NRP 110 (see FIG. 1) on a configurable basis.For example, an MMS might use an IP based ping test to test every IPclass C address that the MMS serviced within the last 7 days. This testmay be repeated on a 5 minute basis, and the results would be forwardedto the NRP 110 and, possibly, to the RTSMS 106 (see FIG. 1). Thetransport latency table 1008 also may contain latency forecastsgenerated from the RTSMS 106.

FIG. 11 depicts an exemplary embodiment of a treatment table accesspoint 1102 for the tables depicted in FIG. 8. The access point to thetreatment table 814 is depicted by incoming access for a reservationrequest, incoming access control for a reservation request, switchidentification and selection, outgoing access control for a reply, andoutgoing access for a reply. The treatment table access point table 1102identified in FIG. 11 depicts typical access points. However, in someinstances, the tables may access the treatment table at other accesspoints.

In the example of FIG. 11, the active reservations table 804 accessesthe treatment table 814 at the incoming access point. The network accesstable 806 accesses the treatment table at the outgoing access point. Thesignal mapping table 808 and the signal access point table 810 typicallymay access the treatment table 814 at the incoming access control pointand the outgoing access control point. The stream control table 812typically accesses the treatment table 814 at the incoming accesscontrol point. The referring host table 816, the exception table 818,the PIN table 820, the content screening table 822, the content locationtable 824, the network status table 826, the day of year table 828, theday of week table 830, and the time of day table 832 typically accessthe treatment table 814 at the switch identification and selectionaccess point. The signal route choice table 834 and the class of servicetable 836 typically access the treatment table 814 at the outgoingaccess control point.

FIGS. 12-29 depict examples of tables described in FIGS. 8-11. It willbe appreciated that other versions of the tables may exist. In addition,information identified in the tables of FIGS. 12-29 may be combined orchanged to form different, additional, or fewer tables.

FIG. 12 depicts an exemplary embodiment of an active reservations table.The active reservations table 1202 of FIG. 12 is used to accessinformation identifying one or more reservations for one or morepresentations. The active reservations table 1202 also is used toprovide information identifying a terminating signaling network pointfor streams originating at other network signaling points or NRPs withina same network, such as the streaming system 102. The reservationidentification (ID) 1204 of the presentation is used to enter the activereservations table 1202.

The active reservations table 1202 contains the order and presentationinformation generated during the reservation process. In the embodimentof FIG. 12, the order information includes the order identification (ID)1206, the order type 1208, and the individual order line 1 1210 to orderline N 1212. An order line, for example, may reference a program for aservice order or may reference a media for a storage order. Otherexamples for other orders exist. Specific rules may exist for the orderline above what the order as a whole contains. For example, a programmay combine several pay-per-view events. This may include a first eventwhere the service is charged every 30 minutes of viewing time and theviewer orders an hour. In another example, a viewer is a subscriber on amonthly basis and purchases a pay-per-view program at a specialpromotion rate because that viewer is a subscriber.

The order lines 1210-1212 can be associated on a one-to-one basis withthe media being streamed to a viewer. For example, if an originatingnetwork cannot deliver a presentation or the remainder of apresentation, the originating network may try to locate one or moreother networks to broker the delivery of the media to the viewer. Theorder data may be used to inform the other network the pricing value ofthe reservation and the estimated fee for providing a streaming serviceto the viewer. Other uses, for example, include determining the routingthrough one or more other networks based on a selected fee structure. Inone embodiment, the presentations that generate more revenue for anetwork owner receive priority during the table processing.

The active reservations table 1202 also contains information identifyingthe buyer of the media. The buyer may be an individual or organizationthat is purchasing media or services, such as a pay-per-viewpresentation, a subscription service, a registration with a portal toview advertising supported content, and/or other media and/or services.The buyer data includes the buyer's identification (ID) 1214, thebuyer's location 1216, and the buyer's network access type 1218. Thebuyer location 1216 may be, for example, an NPA-NXX or a zip code. Thebuyer's network access type 1218 may be, for example, internet, cable,broadband wireless, ATM, or another type.

The buyer data also includes a buyer attribute 1 1220 to buyer attributeN 1222. The buyer attributes 1220-1222 may be configurable by thenetwork owner. For example, the network owner may create buyer profilesbased on data, including age, sex, income level, the amount of businessoccurring between the buyer and the network owner in a period of time,the buyer's viewing and/or purchasing history, and/or other attributes.

The active reservations table 1202 also contains information identifyingthe viewer of the presentation. The viewer may be the same individual orentity as the buyer or another individual or entity. The buyer mayestablish viewer accounts and profiles. For example, a buyer may be ahead of a household and may establish viewers for each of the buyer'schildren and set their viewing profiles accordingly. The viewerinformation may include the viewer identification (ID) 1224, the viewerlocation 1226, and the viewer network access type 1228. The viewerinformation also may include a viewer attribute 1 1230 to a viewerattribute N 1232. The viewer attributes 1230-1232 may include, forexample, age, sex, income level, content screening level, the viewer'sviewing history, and/or other viewer attributes.

The active reservations table 1202 also contains information identifyingthe presentation requirements. The presentation data includes thepresentation identification (ID) 1234, the presentation media servertype 1236, the presentation type 1238, and the program identification(ID) 1240. Alternately, a media identification may be included in placeof the presentation identification in some embodiments. The presentationtype 1238 may be, for example, audio, video, images, a combinationthereof, or another type. The presentation data also includes for eachpiece of media, the media number 1242 and the associated media numbertype 1244 for each media 1 to N. The media number and media number typewill be included for each media in a presentation. Likewise, anassociated resource number 1246 and an associated resource number type1248 will exist for each resource 1 to N.

FIG. 13 depicts an exemplary embodiment of a network access table. Thenetwork access table 1302 of FIG. 13 is used to identify information forpacket network connections. The network access table 1302 is accessedvia a network ID 1304 from the active reservations table 804. The packetaddress closest to the viewer may be used as a default. Although, otherpacket addresses may be used. For example, a buyer's packet address or areferring portal packet address may be used.

A packet address format may be dependant upon the type of transport andthe protocol being used. For example, an internet access would use an IPaddress format. In another example, a cable network using ATM to thehome may use a packet address format identifying a virtual path/virtualcircuit (VP/VC).

The network access table 1302 may contain order information generatedduring a customer set-up process. The order information may contain anorder identification (ID) 1306, and order type 1308, and individualorder lines from order line 1 1310 to order line N 1312. The order lines1310-1312 may be associated on a one-to-one basis with the network ID1304. For example, if the network ID 1304 identifies a buyer's homeaddress, the order lines 1310-1312 might identify the buyer as asubscription customer that is paying for advertising/free viewing. Inanother example, the packet address might identify an internet portalsite and reflect the fee arrangements with that site. The order datatypically reflects the default billing arrangements for the packetaddress that is provided. If no other billing data is generated viaother processes, the default data is used.

The network access table 1302 also contains packet service informationthat is associated with the network ID 1304. In the example of FIG. 13,only one packet service is associated with the network ID 1304. However,multiple packet services and multiple packet protocols may exist and maybe supported. For example, an ATM packet network may use a nativetransport for a VP/VC and also use TCP/IP as an upper protocol layer forits transport device. In this example, two sets of service data would beentered.

Service data may include a transport service type 1314, packet type1316, packet transmission speed 1318, and packet address 1320. Thepacket service type 1314 may include, for example, ATM, frame relay,internet, intranet, cable, and/or another service type. A packet type1316 may identify the packet protocol associated with a network ID 1304,such as high speed digital subscriber line (HSDSL), VP/VC, IP address,and others. The packet transmission speed 1318 identifies the maximumtransport bit rate.

The packet address 1320 may identify the full packet addressing schemeneeded to reach a network end point, such as a VP/VC for an ATMconnection or an IP address for an internet connection. Although, it isnot necessary that the full packet addressing scheme be provided. Thepacket network sometimes dynamically controls the last portion of theaddressing assignment. In that event, the packet address may be only apartial. For example, if an ATM network dynamically assigns the virtualcircuit, then the data contained in the packet address 1320 is thevirtual path. In another example, if an internet customer's ISP uses adynamic host configuration protocol (DHCP) option of the IP protocol,then the packet address 1320 is the IP class C address.

The service information also may contain the packet security type andkey 1322. If the packet address is using a secure connection, thesecurity type and security key, if existent, will be required forencryption and/or decryption. Thus, the security type and any existentsecurity key is stored.

Other packet attributes 1324 may be included. For example, a networkowner might want to add the last time point and quality of service testresults or an indicator that a service is always on.

The network access table 1302 also contains data that associates thenetwork ID to a signal access group. The signal access group 1326 is thekey to enter the signal access point table shown in FIG. 15. Additionalsignal data may include the signal protocol 1328 and anin-band/out-of-band signal indicator 1330. The signal data identifieswhere the billing and service control information for the network ID1304 is transported and in what format.

The network access table 1302 also may contain key data referencing abuyer. The buyer data may include the buyer identification (ID) 1332 anda primary contact identification (ID) 1334. The buyer ID 1332 and theprimary contact ID 1334 may be used for default billing arrangements andcontact information for a location. This buyer information enables anetwork operator to access the information stored in the RTSMS 106 (seeFIG. 1) to obtain a complete set of information identifying the networkID 1304, such as a street address, a billing cycle cut off date, andother general information.

The network access table 1302 also contains data referencing a servicelocation. The service location information may include a servicelocation identification (ID) 1336, service location coordinates 1338, aservice location type 1340, a service location contact identification(ID) 1342, and service attributes 1 to N 1344-1346. The service locationID 1336 and the primary contact ID 1334 are used for contact informationfor the service location. This enables multiple service locations to beestablished under one buyer ID 1332. This service location data alsoenables a network operator to access data in the RTSMS 106 (see FIG. 1)to obtain a complete set of information identifying the servicelocation, such as a street address or other general information.

FIG. 14 depicts an exemplary embodiment of a signal mapping table. Thesignal mapping table 1402 of FIG. 14 is entered using a signal mappingaccess key 1404. The signal mapping access key 1404 may be identifiedusing a signal access point table 810. The signal mapping table 1402will be processed if the signal access mapping key 1404 and anassociated protocol (such as shown in FIG. 15) below contain valid datafor the signal group ID being selected from the signal access pointtable 810.

The signal mapping table 1402 maps data attributes from one protocol toanother. For example, an originating signaling network point may use theIETF RTSP protocol, and a terminating network signaling point may usethe IETF SIP protocol. The signal mapping table 1402 will map dataattributes from the internal reservation format used by the signalingsystem 102 to the corresponding data attribute names for the SIPprotocol and/or the RTSP protocol.

In another embodiment, an incoming signaling protocol might use aproprietary API, and the signal mapping table 1402 will map dataattributes from the API protocol to the internal reservation format usedby the signaling system 102. Signal message conversion may occur oninbound signaling, outbound signaling, or in both directions if needed.Thus, the signal mapping table 1402 contains the first reservationattribute name 1408 to the Nth reservation attribute name 1410.Likewise, the signal mapping table 1402 contains the corresponding firstprotocol attribute name 1412 to the Nth protocol attribute name 1414.

The signal mapping table 1402 also identifies routines for encoding anddecoding protocols. The routines are located in the encode library name1416 and the decode library name 1418. Routines are processes thatconvert data attributes from one protocol to another protocol andprovide other protocol rule enforcement. For example, a protocol, suchas the IETF SIP protocol, may specify time frames for a response andsend data in multiple transmissions. The routines monitor these types ofrules and handle any signaling errors that might result from impropermessage formats, improper send/receive timing of messages, such as atime out, and other protocol specific logic that is required.

FIG. 15 depicts an exemplary embodiment of a signal access point table.The signal access point table 1502 provides signaling data for one ormore groups of network access points. Entries are made into the signalaccess point table 1502 using a signal group identification (ID) 1504.

The signal access point table 1502 assigns one or more unique signalpoint codes 1506 to each signaling device registered to providestreaming service. A signal point code is associated with every recordin the network access table 806 that transmits any form of signalingdata. Information identifying the physical location of a signaling pointis collected. In the example of FIG. 15, the physical locationinformation may include signal point coordinates 1508, such as verticaland horizontal coordinates that normally would be present in an IP basedsignaling device, such as a router or a DNS server. Optionally, anNPA-NXX 1512 associated with a service site phone number, a time zone1514, and a signal time zone 1516 associated with the location of thesignaling device may be stored.

The signal access point table 1502 includes order reference informationand default billing information. The order reference and default billinginformation may be used to determine how streaming costs are to beallocated. The order reference and billing information identified inFIG. 15 includes an order identification (ID) 1518, an order type 1520,and order lines 1 to N 1522-1524. In one example, the order ID 1518,order type 1520, and order lines 1522-1524 may be used during a streamconnection processing to inform another signaling network point howbilling for this streaming service transaction is to take place betweentwo separate networks that are being required to deliver the streamingservice. In another example, the order information may be used withinthe streaming system 102 to assign costs to different departments for aprofit/loss analysis.

The signal access point table 1502 also includes information identifyingthe protocols used for signaling over a packet link. The example of FIG.15 depicts only one protocol. However, multiple protocols and multipleprotocol attributes may be used for a single packet link or multiplepacket links. The protocol information includes an identification of thesignal access point associated protocol 1526. The associated protocoldefines what protocol is being referred to for the protocol attributes.An out-of-band identifier 1528 is set when a protocol uses a separatepacket link or communication transport than is being used to deliver thestreaming service. A signal mapping access key 1530 identifies a link tothe signal mapping table 808. A treatment of the partition code 1532identifies the link into the treatment table 814 for error handling or arejection of service. The packet address 1534 and the signal securitytype/key 1536 also may be obtained for the signaling network point.

The signal access point table 1502 also includes operational data for asignaling network point. The operational data may be used by a networkoperator to manage signaling traffic links. The signal point status 1538informs a network operator if the signal link is operational, notoperational due to a scheduled maintenance or other reason, or is in analarm status. The signal point capacity load 1540 typically identifies apercentage variable that a network operator sets to establish the bytesper second to be transmitted across the signaling link. For example, anetwork owner may set the signal point capacity load 1540 to between33-38 percent. Once a signaling link reaches the identified capacity,another signaling route will be selected unless none exist. Other rangesmay be selected.

The signal location type 1542 is identified as well as a class ofservice partition code 1544. The class of service partition codetypically is one-half of a key to a class of service table 836. Thesecond half of the key to the class of service table 836 typically isfound on a corresponding signal group record for the other signalingnetwork point. This enables the routing data structure 802 to determineif the signaling protocols on each signaling network point arecompatible either directly or via a conversion process. The networkowner also can configure other signal point attributes 1 to N 1546 to beplaced in the signal access point table 1502 to aid in the management ofthe signaling network.

FIG. 16 depicts an exemplary embodiment of a stream percent skippedtable. In the stream percent skipped table 1602 of FIG. 16, a partitioncode 1604 is used to enter the table. The network identification (ID)1606 is the second portion of the key to enter the table and can enablethe identified percent to skip control to be applied only to thatnetwork. If the network ID 1606 is left blank, the control will beapplied to all traffic accessed by the partition code 1604. The percentto skip 1610 is the control percentage that specifies the percentage ofincoming streams that will be affected by the control. The next function1612 allows attempts for a stream connection to be routed to anothertable during stream processing. The next partition 1614 points to anarea within the next function table for further stream processing.

FIG. 17 depicts an exemplary embodiment of a stream rate table. Thestream rate table 1702 uses a partition code 1704 to enter the table.The network identification (ID) 1706 can be used as a secondary key thatenables the stream rate control to be applied only to those streamsoriginating from the network ID. If the network ID 1706 is left blank,the stream rate control will be applied to all traffic that accesses thestream rate partition code 1704. The stream rate 1710 specifies thenumber of streams that will be passed by the control on or forcompletion of processing. This information will be used to determine ifan incoming reservation falls within the stream rate control. The nextfunction 1712 allows attempts for a stream connection to be routed toanother table during stream processing. The next partition 1714 pointsto an area within the next function table for further stream processing.

FIG. 18 depicts an exemplary embodiment of a treatment table. Thetreatment table 1802 of FIG. 18 is entered using a partition code 1804.The error number 1806 specifies an error code received duringprocessing. The error number 1806 will be processed for a givenpartition code 1804. This enables the network owner the ability tohandle the same error differently depending on error conditions. Forexample, a viewer attempting to view restricted content may be handledusing a variety of approaches. In a first example, the viewer mayattempt to see restricted content during peak network load hours. Thenetwork owner may send the reservation request to treatment so that atext message requiring fewer network resources is displayed. In anotherexample, the viewer may attempt to see restricted content duringnon-peak load hours. The network owner may send the reservation requestto treatment so that a video-based message is streamed to the viewerexplaining that the buyer of the service has restricted the content frombeing viewed.

The exception table 1802 also contains an error class 1808 for thepartition code 1804. The error class 1808 may be used when sending anerror message via an open system network management standard, such aswith SNMP or CMIP. The error partition code 1810 combined with the errorclass 1808 may be used to access a detailed description of the error.The message media identification (ID) 1812 identifies the message thatwill be streamed by an MMS if a network owner desires a video and/oraudio message to be generated to the viewer. The next function 1814 andnext partition 1816 identify the next table and area within the tablefor further stream processing.

FIG. 19 depicts an exemplary embodiment of a referring host table. Thereferring host table 1902 is used to route traffic based on theoriginating network owner or a URL. The referring host partition code1904 is used to enter the referring host table 1902. Different routingalgorithms may be created and stored for the same referring location bycreating multiple referring host partition codes for the same location.

The referring host table 1902 contains an element identification (ID)1906 that is generated as an identifier by the RTSMS 106 (see FIG. 1).The element ID 1906 describes the type of referring device for thisrecord. A referring device may be, for example, a website URL, a set topbox, a cable network head, or another packet network capable oforiginating streaming requests. The referring site reference 1908 is theidentification of the location originating the streaming request. Thereferring site reference may be, for example, a web portal, apay-per-view cable head, the medium access control (MAC) address of theset top box at a customer's home, or another identification.

The referring host service type 1910 designates whether the referringhost is a public internet service, a corporate intranet service, aprivate network delivery service, such as a cable or satellite network,or another type of service. The next function 1912 allows attempts to berouted to another table during stream processing. The next partition1914 points to an area within the next function table for further streamprocessing.

The referring host table 1902 also contains order information generatedduring the referring host customer set up process. The order informationcontains the order identification (ID) 1916, the order type 1918, andorder lines 1 to N 1920-1922. The order information can be associated ona one-to-one basis with the referring host partition code 1904. Theorder information typically reflects the default billing arrangement forthe partition code 1904. If no other billing data is generated via otherprocesses, the billing data in the referring host table 1902 is used.For example, information designating a URL referral fee may be containedin the order information if the reservation request has to be passed toanother network. In this example, the other network signaling point maybe informed of the costs of processing the reservation request.

FIG. 20 depicts an exemplary embodiment of an exception table. Theexception table 2002 is accessed by using an exception partition code2004. The exception table 2002 is used to route streaming requestsaround default routing. The exception element identification (ID) 2006defines the type of element. For example, the element may be a mediaplayer type, a packet address, a content type, or another element type.These items may require special handling, such as when an older mediaplayer version is not compatible with installed media server software.

The player type 2008 identifies the type of media player being used onthe device streaming the media. The player type may be, for example, aWindows Media Server or a proprietary set top box player used by asatellite company or a cable company. The player version number 2010identifies the media player version. The media type 2012 identifiesrouting based upon the type of file being requesting. The media type maybe, for example, MPEG standard 1, MPEG standard 2 (MPEG-2), MPEGstandard 4 (MEG-4), Microsoft ASF, or other encoding standards formedia.

The network access type 2014 identifies the type of originating accessthe viewer is using. The network access type 2014 may be, for example, acable modem, a cable set top box, an ISP for the internet, or anothertype. The packet address from range 2016 and packet address to range2018 are used to route a stream reservation request based upon thepacket address. For example, a cable company may deny a pay-per-viewrequest from a set top box owner that is in arrears for the owner'sbilling account. The set top box packet addresses for all boxesinstalled in the house may be blocked using this feature. The nextfunction 2020 allows streaming attempts to be routed to another tableduring stream processing. The next partition 2024 points to an areawithin the next function table for further stream processing.

FIG. 21 depicts an exemplary embodiment of a PIN table. The PIN table2102 is used to provide information identifying a viewer's equipmentand/or media player software. The PIN table 2102 is accessed via the PINpartition code 2104. A different routing algorithm may be created andstored for the same referring location by creating multiple PINpartition codes for the same location. The element identification (ID)2106 is an identifier generated by the RTSMS 106 (see FIG. 1). Theelement identification describes the type of PIN device or software forwhich this record was generated. The PIN device or software may be, forexample, a Real Network Real Player, a set top box software key, apacket address, a web cookie identifier, or another deviceidentification technique. The identifier further may include the elementversion number 2108 and/or the player identification (ID) 2110.

The packet address from range 2112 and packet address to range 2114 areused to route stream requests based upon packet addresses. For example,a company might insert an advertisement for a video game. It must becompatible with the device or software identified by the element ID2106. In some cases, a treatment label 2116 may be provided for accessto the treatment table 814. Additionally, other attributes may be addedto the table where needed. The next function 2118 allows attempts to berouted to another table during streaming processing. The next partition2120 points to an area within the next function table for further streamprocessing.

FIG. 22 depicts an exemplary embodiment of a content screening table.The content screening table 2202 performs functions similar to thereservation system described in FIG. 2. However, the content screeningtable 2202 performs functions that are directly controlled by devices ofthe network operator in the event that a management system, such as theRTSMS 106 (see FIG. 1), fails. The content screening table 2202 isaccessed using a content screen partition code 2204. A different routingalgorithm may be created and stored for the same location by creatingmultiple content screening partition codes for a same location.

An element identification (ID) 2206 is an identifier generated by theRTSMS. The identifier describes the type of content being screened. Thecontent being screened may be, for example, a program, a media ratingtype, such as the Motion Picture Association's (MPA) NC-17 rating,picture images, and other content types. The media identification (ID)2208 allows a specific media to be identified within all presentations.Special routing may be applied for such media. For example, if a networkowner receives consumer complaints regarding a particular media, thenetwork owner may block access to the media using the media ID 2208,even though the media may be listed in numerous programs andpresentations.

The media rating 2210 enables routing content based upon its ratingassigned by, for example, independent monitoring groups, such as theMPA. The program ID from range 2212 and the program ID to range 2214 areused to route programs within the identified range of IDs. The nextfunction 2216 enables attempts to be routed to another table duringstream processing. The next partition 2218 points to an area within thenext function table for further stream processing.

FIG. 23 depicts an exemplary embodiment of a content location table. Thecontent location table 2302 may be cached in memory and used to locatewhere media is stored throughout a network, such as the streaming system102. The content location table 2302 stores information identifyingindividual media and media clips that are to be delivered to a viewer.The media identification (ID) 2304 is used as a key to enter the contentlocation table 2302.

The media category 2306, media class 2308, media rating 2310, and medialength 2312 also are included. The media category 2306 may be, forexample, a television series, a movie, a music video, or other mediacategories. The media class 2308 represents a second level ofclassification. For example, the television series category might havefinancial programs, world news, soap operas, comedies, or otherclassifications. The media rating 2310 may be, for example, a ratingbased on a monitoring group, such as the MPA. The media length 2312identifies how long the media takes to stream, such as an estimatednumber of seconds.

The encode rate 2314 identifies the bytes per second of a packettransmission required to view the media. The disk size 2316 is theamount of disk space required to store the media. The content locationorder identification (ID) 2318 refers to a storage order that can belocated in a management system, such as the RTSMS 106. The storage orderrefers to how much a media owner is being charged to store the media onthe signaling system 102. A media file name 2320 may be associated withthe storage order and the order ID 2318. The switch identification (ID)2322 identifies one or more MMSs that contain the media identified bythe media file name 2320. The network owner may append other mediaattributes 1 to N 2324 to use for the content location table 2302.

FIG. 24 depicts an exemplary embodiment of a network status table. Thenetwork status table 2402 typically is cached in memory and reflects thecurrent status of all devices required to connect a streaming service. Aswitch identification (ID) 2404 is used to enter the network statustable 2402. Multiple resources are monitored for each switch, causingmultiple entries per switch to be entered into the table. Although, inthe example of FIG. 24, a single row is depicted.

The secondary key for the network status table 2402 for each row is theresource type 2406. The resource type identifies the resource beingmonitored and may include, for example, the public packet to bandwidth,signaling bandwidth, disk storage, processor use, and/or otherresources. Each resource has an available resource capacity 2408 and acurrent capacity use 2410 of the resource. The current resource state2412 also is depicted, such as whether the resource is in a maintenancestate, an alarm state, or is available for use. The network owner mayappend other attributes from 1 to N 2414 to the network status table.

FIG. 25 depicts an exemplary embodiment of a day of year table. The dayof year table 2502 is accessed by using a day of year partition code2504. The from date 2506 and to date 2508 indicates the local date asapplicable to the action to be taken during the processing of thistable. The next function 2510 enables attempts to be routed to anothertable during stream processing. The next partition 2512 points to anarea within the next function table for further stream processing.

FIG. 26 depicts an exemplary embodiment of a day of week table. The dayof week table 2602 is entered using a day of week partition code 2604.The from day 2606 and to day 2608 indicate the local days of the week onwhich the action to be taken is to occur. The next function 2610 enablesattempts to be routed to another table during stream processing. Thenext partition 2612 points to an area within the next function table forfurther stream processing.

FIG. 27 depicts an exemplary embodiment of a time of day table. The timeof day table 2702 is accessed using a time of day partition code 2704.The from time 2706 and to time 2708 indicate the local times duringwhich an action is to be taken. That is, the entries indicate the timein which an action is to start and a time at which an action is to stop.The next function 2710 enables attempts to be routed to another tableduring stream processing. The next partition 2712 points to an areawithin the next function table for further stream processing.

FIG. 28 depicts an exemplary embodiment of a signal route choice table.The signal route choice table 2802 is accessed using a signal routechoice partition code 2804. The route number 2806 specifies a routewithin a routing list. The route choices for a given route label will beprocessed in the order indicated by the route numbers. Therefore, thesignal route choice table 2802 is used to prioritize route choices. Forexample, a first network, such as the streaming system 102, may beconnected to two other networks and delivery terms have been negotiatedwith each. The network providing the most favorable billing rate to thefirst network may be selected as the first route choice. The nextfunction 2808 enables attempts to be routed to another table duringstream processing. The next partition 2810 points to an area within thenext function table for further stream processing.

FIG. 29 depicts an exemplary embodiment of a class of service table. Theclass of service table 2902 is accessed using an originating signalclass of service partition code 2904 and a terminating signal class ofservice partition code 2906. The next function 2908 enables attempts tobe routed to another table during stream processing. The next partition2910 points to an area within the next function table for further streamprocessing.

Those skilled in the art will appreciate that variations from thespecific embodiments disclosed above are contemplated by the presentinvention. The invention should not be restricted to the aboveembodiments, but should be measured by the following claims.

What is claimed is:
 1. A method for routing media comprising: receivinga request for media; determining, at least one computing device, aprogram in which the requested media is identified; creating, at the atleast one computing device, a presentation having a presentationidentification based on the program; generating, at the at least onecomputing device, a play script comprising at least one mediaidentification for the requested media; receiving the at least one mediaidentification at a routing processor; at the routing processor,determining a media switch configured to stream media identified by themedia identification; generating an address for the media switch upondetermining the media switch; and streaming, over a communicationnetwork, the media identified by the media identification from the mediaswitch upon a session being initiated at the address.
 2. A method forrouting media for reception by a viewer for a request comprising:identifying at least one program in which at least a portion of themedia is available; processing the request with at least one programrule of the at least one program to generate a presentation identifyingthe at least the portion of the media; generating a reservationassociated with the presentation; and identifying at least one resourceto stream the presentation over a communication network for reception bythe viewer based on the reservation.
 3. The method of claim 2 furthercomprising: identifying at least one other program in which at least oneother portion of the media is available; processing the request with atleast one other program rule of the at least one other program togenerate at least one other presentation identifying the at least oneother portion of the media; generating at least one other reservationassociated with the at least one other presentation; and identifying,based on the at least one other reservation, if the at least oneresource is configured to stream, over the communication network, the atleast one other presentation.
 4. The method of claim 2 furthercomprising: identifying at least one other program in which at least oneother portion of the media is available; processing the request with atleast one other program rule of the at least one other program togenerate at least one other presentation identifying the at least oneother portion of the media; generating at least one other reservationassociated with the at least one other presentation; and identifying,based on the at least one other reservation, at least one other resourceto stream, over the communication network, the at least one otherpresentation.
 5. The method of claim 2 further comprising: identifyingat least one other program in which at least one other portion of themedia is available; processing the request with at least one otherprogram rule of the at least one other program; and generating thepresentation identifying the at least one portion of the media and theat least one other portion of the media.
 6. The method of claim 2further comprising: generating a presentation identification for thepresentation and a reservation identification for the reservation; andgenerating the presentation, the presentation identification, and thereservation identification as the reservation.
 7. The method of claim 2further comprising applying a viewer profile to the at least one programto generate the presentation.
 8. The method of claim 2 furthercomprising generating a play script for the presentation for the viewer,the play script comprising at least one media reference identifying theat least one portion of the media.
 9. The method of claim 8 whereingenerating the play script further comprises generating the play scriptwith a plurality of media references identifying a plurality of media.10. The method of claim 8 further comprising generating the at least onemedia reference to identify at least one media clip and a reservationidentification for the reservation.
 11. The method of claim 8 furthercomprising generating the at least one media reference to comprise auniversal resource locator that identifies at least one media clip and areservation identification for the reservation.
 12. The method of claim8 further comprising generating the at least one media reference tocomprise at least one member of a group consisting of a recorded mediareference, a live media reference, a media alias, and a media selector.13. The method of claim 8 further comprising formatting the play scriptaccording to a player type for the viewer.
 14. The method of claim 8further comprising transmitting an address of the at least one resourceto for reception by the viewer.
 15. The method of claim 2 wherein the atleast one resource comprises a switch and the method further comprises:distributing the at least one program to the switch; selecting theswitch to stream the presentation for reception by the viewer; andstreaming, over the communication network, the at least one portion ofthe media from the switch for reception by the viewer.
 16. The method ofclaim 2 further comprising selecting the resource from at least onemember of a group consisting of a switch, a media server software of theswitch, and a stream caster of the switch.
 17. The method of claim 2wherein: the at least one program has a program identification; and themethod further comprises tracking the program by the programidentification using a management system.
 18. The method of claim 17further comprising using the program identification to track at leastone member of a group consisting of a number of times a selected mediaof the at least one program is streamed over the communication network,or another number of times the at least one program is streamed over thecommunication network, a viewer attribute associated with the viewerreceiving the selected media from the at least one program, and at leastone other media from at least the other program streamed with the atleast one portion of the media.
 19. The method of claim 2 furthercomprising using as the at least one program rule at least one member ofa group consisting of a program creation rule and a program routingrule.
 20. The method of claim 2 further comprising using at least oneorder comprising at least one order component associated with the atleast one program to process the request and generate the presentation.21. The method of claim 20 further comprising using as the at least oneorder component at least one member of a group consisting of a servicerule identifying how a media viewing should be paid, a storage ruleidentifying where the media and the program will be located for physicalstorage, a collection rule identifying an entity collecting a paymentfor services rendered, a viewing rule identifying acceptable viewersthat can receive the media and the program, and a settlement ruleidentifying how a collection is divided among participating entities.22. The method of claim 20 further comprising using a service processorto enable entry of the at least one program and the at least one orderfor the at least one program.
 23. A system for routing media for arequest for a viewer comprising: a communication network; a managementsystem configured to receive the request for media, to determine aprogram in which the requested media is identified, to create apresentation having a presentation identification based on the program,to generate a reservation comprising a reservation identification andthe presentation, and to generate a play script comprising thereservation identification and at least one media identification for therequested media; a media switch configured to stream, over thecommunication network, media identified by the at least one mediaidentification upon a session being initiated at an address; and arouting processor configured to receive the reservation, the reservationidentification, and the media identification, to validate thereservation identification with the reservation, to determine the mediaswitch configured to stream, over the communication network, the mediaidentified by the at least one media identification, and to generate theaddress for the media switch upon validating the reservationidentification.
 24. A system for routing media for reception by a viewerfor a request comprising: a communication network; a reservation systemto receive the request, to identify at least one program in which atleast a portion of the media is available, to process the request withat least one program rule of the at least one program to generate apresentation identifying the at least the portion of the media, and togenerate a reservation associated with the presentation; and a routingprocessor to receive the reservation from the reservation system and toidentify, based on the reservation, at least one resource to stream thepresentation over the communication network for reception by the viewer.25. The system of claim 24 wherein: the reservation system further isconfigured to identify at least one other program in which at least oneother portion of the media is available, to process the request with atleast one other program rule of the at least one other program togenerate at least one other presentation identifying the at least oneother portion of the media, and to generate at least one otherreservation associated with the at least one other presentation; and therouting processor further is configured to receive the at least oneother reservation from the reservation system and to identify, based onthe at least one other reservation, if the at least one resource isconfigured to stream, over the communication network, the at least oneother presentation.
 26. The system of claim 24 wherein: the reservationsystem further is configured to identify at least one other program inwhich at least one other portion of the media is available, to processthe request with at least one other program rule of the at least oneother program to generate at least one other presentation identifyingthe at least one other portion of the media, and to generate at leastone other reservation associated with the at least one otherpresentation; and the routing processor further is configured to receivethe at least one other reservation from the reservation system and toidentify, based on the at least one other reservation, at least oneother resource to stream, over the communication network, the at leastone other presentation.
 27. The system of claim 24 wherein thereservation system is configured to identify at least one other programin which at least one other portion of the media is available, toprocess the request with at least one other program rule of the at leastone other program, to generate the presentation, and to generate thereservation associated with the presentation, wherein the presentationidentifies the at least the portion of the media and the at least oneother portion of the media.
 28. The system of claim 24 wherein thereservation system is configured to generate a presentationidentification for the presentation and a reservation identification forthe reservation, and the reservation comprises the presentation, thepresentation identification, and the reservation identification.
 29. Thesystem of claim 24 wherein the reservation system is configured to applya viewer profile to the at least one program to generate thepresentation.
 30. The system of claim 24 wherein the reservation systemfurther is configured to generate a play script for the presentation forthe viewer, the play script comprising at least one media referenceidentifying the at least the portion of the media.
 31. The system ofclaim 30 wherein the play script comprises a plurality of mediareferences identifying a plurality of media.
 32. The system of claim 30wherein the media reference identifies at least one media clip and areservation identification for the reservation.
 33. The system of claim30 wherein the media reference comprises a universal resource locatorthat identifies at least one media clip and a reservation identificationfor the reservation.
 34. The system of claim 30 wherein the mediareference comprises at least one member of a group consisting of arecorded media reference, a live media reference, a media alias, and amedia selector.
 35. The system of claim 30 wherein the play script isformatted according to a player type for the viewer.
 36. The system ofclaim 30 wherein the routing processor further is configured to transmitan address of the at least one resource for reception by the viewer. 37.The system of claim 24 wherein the at least one resource comprises aswitch configured to stream the at least the portion of the media forreception by the viewer, wherein the service processor further isconfigured to distribute the at least one program to the at least oneswitch, and wherein the routing processor further is configured toselect the switch to stream the presentation to the viewer.
 38. Thesystem of claim 24 wherein the resource comprises at least one member ofa group consisting of a switch, a media server of the switch, and astream caster of the switch.
 39. The system of claim 24 wherein: the atleast one program has a program identification; and the system furthercomprises a management system configured to track the program by theprogram identification.
 40. The system of claim 39 wherein themanagement system is configured to use the program identification totrack at least one member of a group consisting of a number of times aselected media of the at least one program is streamed over thecommunication network, another number of times the at least one programis streamed over the communication network, a viewer attributeassociated with the viewer receiving the selected media of the at leastone program, and at least one other media from at least one otherprogram streamed over the communication network with the at least theportion of the media.
 41. The system of claim 24 wherein the at leastone program rule comprises at least one member of a group consisting ofa program creation rule and a program routing rule.
 42. The system ofclaim 24 wherein the at least one program further comprises at least oneorder consisting of at least one order component.
 43. The system ofclaim 42 wherein the at least one order component comprises at least onemember of a group consisting of a service rule identifying how a mediaviewing should be paid, a storage rule identifying where the at leastthe portion of the media and the program will be located for physicalstorage, a collection rule identifying an entity collecting a paymentfor services rendered, a viewing rule identifying acceptable viewersthat can receive the at least the portion of the media and the program,and a settlement rule identifying how a collection is divided amongparticipating entities.
 44. The system of claim 42 further comprising aservice processor configured to enable entry of the at least one programand the at least one order for the at least one program.
 45. The methodof claim 1, wherein the communication network comprises a wirelessnetwork.
 46. The method of claim 2, wherein the communication networkcomprises a wireless network.
 47. The system of claim 23, wherein thecommunication network comprises a wireless network.
 48. The system ofclaim 24, wherein the communication network comprises a wirelessnetwork.